I am attempting to create an SDK for a CE 5.0 platform. I have previously
done this a few years back for this exact platform but a few custom headers
have been added since, and it is time to regen a new SDK.
After creating and configuring the SDK and then attempting to create the SDK
I receive the following message dialog box...
"It is recommended that you build a run-time image before building an SDK.
Otherwise, the build process for your SDK might not succeed. Do you want to
continue?"
The error after selecting "Build SDK . . ." is the following:
---------------------------------
Committing database changes
Creating 'required' feature
Adding required files
Committing database changes
Rolling sysgen'ed headers and libs
*MY_PLATFORM_NAME*: ARMV4I_Release
Error: This build configuration has not been sysgen'ed
Error adding sysgen'ed headers and libs
Error rolling toolkit-specific files
MSI file construction completed. 3 error(s), 0 warning(s).
---------------------------------------
I should mention that I have indeed Sysgened and have a run-time image for
the platform, reboot the build machine and rebuilt, cleaned up the build
tree, pulled new source, rebuilt, etc. and still get the same error. FWIW,
this is an Armv4i (xScale) platform.
Thoughts?
Hi ,
I too faced similar error earlier i got it resolved by first
"build and Sysgen" my Project and only then Build SDK for it.
Without Build and sysgen it wont be able to create binaries/libs reqd
by sdk.
On Jul 30, 12:42 am, FoolBlah <foolb...@discussions.microsoft.com>
wrote:
> I am attempting to create an SDK for a CE 5.0 platform. I have previously
> done this a few years back for this exact platform but a few custom headers
[quoted text clipped - 32 lines]
>
> Thoughts?
Tom Gensel (eMVP) - 30 Jul 2008 07:43 GMT
Nearly once a week there is a post in this newsgroup by an experienced
CE developer explaining why you should NEVER DO a "Build and Sysgen"
and even how to remove the menu command from the tools so that it
can't be accidentally selected. For more explanation on why this is
the case just review any of the recent threads on that topic.
FoolBlah, you may want to check this page for some suggestions from MS
on this. Hope it helps -
http://support.microsoft.com/kb/906459
Tom
>Hi ,
> I too faced similar error earlier i got it resolved by first
[quoted text clipped - 40 lines]
>>
>> Thoughts?
Thanks Tom.
NEVER do a *Build and Sysgen*, badness will ensue...
I feel as if I am an "experienced CE developer" so I ask, why has this
*feature* been part of every PB release in recent history (maybe forever?)
and why does it continue to be in the latest CE 6.0 PB release? If it is
never to be used, why does MS continue to provide it?
I can see how it may add a bit of flexibility if PB is being used outside of
the "standard usage model" but for those unknowing it can reek havoc.
Thanks.
> I am attempting to create an SDK for a CE 5.0 platform. I have previously
> done this a few years back for this exact platform but a few custom headers
[quoted text clipped - 32 lines]
>
> Thoughts?
Michel Verhagen (eMVP) - 30 Jul 2008 12:51 GMT
Hey Foolblah, join the club!
We (eMVP's) have protested against this build option for years, but it's
simply not a priority to remove it since you can remove it yourself. I
must say that I was surprised to see this menu item in CE 6.0 again, but
hey, it's just one of those things I suppose...
Good luck,
Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog
GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
> Thanks Tom.
>
[quoted text clipped - 46 lines]
>>
>> Thoughts?
Paul G. Tobey [eMVP] - 30 Jul 2008 16:16 GMT
When the Microsoft engineers want to do a complete build of the OS for
distribution to us (or testing or anything else), they would use Build &
Sysgen (it builds everything, which needs to happen). It's just a guess,
but I think that they have, in the past, tried very hard to avoid making
slightly different versions of PB for MS and the rest of the world, which is
a very good idea, but this is the pain point where that strategy has a
problem.
Paul T.
> Thanks Tom.
>
[quoted text clipped - 54 lines]
>>
>> Thoughts?