Tailored SDK for XPe

  • Thread starter Thread starter Hans de Vetten [PTS Software]
  • Start date Start date
H

Hans de Vetten [PTS Software]

Hi,

On Windows CE you can (must) export a SDK containing only those parts that
are actually available on your runtime. I was wondering whether something
like that can be done with XPe or if some tool exists that does this for
you?
The size of your runtime can greatly benefit from this, because developers
are not allowed to use anything (MFC or .NET etc) when it is not in the
runtime.

Regards,
Hans de Vetten
PTS Software
 
On Windows CE you can (must) export a SDK containing only those parts that
are actually available on your runtime. I was wondering whether something
like that can be done with XPe or if some tool exists that does this for
you?
Click to expand...

This sounds like Target Designer.
But you can't make such a clean cut to export exact set of API functions
that you want.
You can include components that bring functionality like (services, drivers,
dll's) but impact on Win32 subsystem will be small.
Or if you are basing XPE to kernel mode only, then you will have small image
but yuo will only have kerler API documented in DDK.
The size of your runtime can greatly benefit from this, because developers
are not allowed to use anything (MFC or .NET etc) when it is not in the
runtime.
Click to expand...

This is high level thing and you don't have to include it. (You can leave it
out)

Best regards,
Slobodan
 
You have a good suggestion for future releases, but this is only a feature
of CE. You will have to document for users what service components you have
included in your configuration.

Regards,

Sean Liming
www.a7eng.com
Author: Windows NT Embedded Step-By-Step and XP Embedded Advanced.
 
I must admit that I have completely misunderstood the original question.
Probably because I have never used WinCE.
You have a good suggestion for future releases, but this is only a feature
of CE. You will have to document for users what service components you have
included in your configuration.
Click to expand...

It would be almost impossible to say what components will give exactly what
functionality. Currently MS is struggling with finding and breaking
dependencies between components.
And you want during the build to have complete manifest of supported
functions and interfaces, ActiveX controls, DirectShow components, driver
functionality, etc.
How Win XP is currently implemented this sounds like SF to me because it is
too complex.

If only that you want is the list or used components to print then this is
other issue.

Best regards,
Slobodan
 
Hans,

There is no such SDK export functionality build-in XPe. I think the main
reason is that XPe goes without any SDK. When you build XPe runtime you
basically just compact XP Pro binaries from selected components in a few
directories+registry hives.
WinCE build is different. Each CE component goes with the set of .lib, .h
files (SDKs) that allows developers to build the final runtime's SDK
(cesysgen/sdk/inc and cesysgen/sdk/lib).
The only way for XPe to have the feature would be for MS to go through
Platform SDK and assigned appropriate SDK components (.h and .lib and etc.)
to each XPe component. This process seemes to be very difficult if it's
started from scratch.

However, only MS may give you the final word on if the feature is in the
future plans for XPe.

KM

HdV> Hi,

HdV> On Windows CE you can (must) export a SDK containing only those
HdV> parts that are actually available on your runtime. I was wondering
HdV> whether something like that can be done with XPe or if some tool
HdV> exists that does this for you?
HdV> The size of your runtime can greatly benefit from this, because
HdV> developers are not allowed to use anything (MFC or .NET etc) when
HdV> it is not in the runtime.

HdV> Regards,
HdV> Hans de Vetten
HdV> PTS Software


With best regards, KM. E-mail: (e-mail address removed)
 
Back
Top