Create Account
Search
You are here: TDG Forum  >>  Board Support Packages (BSP)  >>  Windows CE  >>   Unable to create an SDK using PB 5.0

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Sep 2007 07:30 AM by  ThomasHill
Unable to create an SDK using PB 5.0
 8 Replies
Sort:
You are not authorized to post a reply.
Author Messages
dadawan@gmail.com
New Member
New Member
Posts:


--
26 Mar 2007 11:53 AM
    I have a LPD pxa270 development kit, and the lpd Windows CE BSP for it. It is working great so far.

    However, I wanted to make an SDK so that applications could be developed using Visual Studio 2005 perhaps on machines which don't have Platform Builder installed.

    Following the instructions in the PB help file, I configured the SDK, but when I try to build it I get the following error:

    "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?"

    Obviously, I tried building again to no avail...

    I searched around and found the following link from Microsoft which was promising but in end did not solve my problem:

    http://support.microsoft.com/kb/906459

    I can get by with using the SDK provided by LPD, but I should be able to make my own custom SDK which more accurately reflects what I put in my OS image, shouldn't I?

    -Kevin
    casner
    New Member
    New Member
    Posts:


    --
    02 Apr 2007 07:52 PM
    When it says you need to build a runtime image, it means the Sysgen on the Build OS menu, not Build SDK on the Platform menu. I assume that you have configured a runtime image using items from the catalog. You should build at least a release image of the OS before Building an SDK. That way all the pieces are in the Release directory for the SDK builder to build its image from.

    I like to build a debug image as well if I can fit it in memory, so when the person without PB can debug applications more completely. The SDK builder will take whatever OS image(s) you have built and package it up as an SDK.
    dadawan@gmail.com
    New Member
    New Member
    Posts:


    --
    03 Apr 2007 08:06 AM
    Thanks for your answer.

    I did realize that it wants me to Sysgen and build a OS image before building the SDK. However, I still get this message. I verified it again this morning that I can do a Sysgen and upon successful completion the SDK Build fails with that message.

    -Kevin
    casner
    New Member
    New Member
    Posts:


    --
    03 Apr 2007 08:30 AM
    I assume your build of the OS has no errors, downloads and runs. And that you have followed the steps in the MS KB you referenced.

    There are quite a few choices in the SDK Config menu. The Install, CPU, Transports and Startup Servers are the only pages I have changed/checked, and mostly I left defaults.
    dadawan@gmail.com
    New Member
    New Member
    Posts:


    --
    04 Apr 2007 09:21 AM
    I am working with two different OS images, one with lots of stuff including the Web browser, sound support, web server, .net compact framework etc.

    The other os image is minimal, with USB support. Strangely enough I can make an SDK for this OS image, but not the larger one.

    -Kevin
    casner
    New Member
    New Member
    Posts:


    --
    04 Apr 2007 09:50 AM
    Does the larger OS actually load and run on your target? I'm betting you probably can't build a debug version without memory problems, unless your board has 128M.

    An SDK build won't work unless the Sysgen builds successfully. Preferably it should also load into the target and run.

    One thing you could look at is the SysgenSettings.out files for the two different builds.
    dadawan@gmail.com
    New Member
    New Member
    Posts:


    --
    05 Apr 2007 01:05 PM
    Yes, both OS images build fine and run fine.



    I searched around and found the following link from Microsoft which was promising but in end did not solve my problem:

    http://support.microsoft.com/kb/906459


    -Kevin
    freem
    New Member
    New Member
    Posts:


    --
    10 Sep 2007 02:33 PM
    Did you ever get the SDK to build? I am having the same problem. I believe it to be .NET2.0. When I add it to to working project, that both the Sysgen and SDK work, the will SDK stop working with that error message. Once the project has this error I have never been able to make it go away.
    ThomasHill
    New Member
    New Member
    Posts:


    --
    11 Sep 2007 07:30 AM
    This may not help you, since you're probably wanting the .NET stuff. But since I am building my app with VS2005, I thought I might pass this along for what it's worth.

    I'm doing C++/MFC. I build a CE image without the MFC support, but add my own catalog item that includes msvcr80.dll, atl80.dll, and mfc80u.dll. I don't use a browser, but I do include the IE browser control host and the HTML/DHTML API in order to view our help files written in HTML.

    Having looked at that link you posted, I have a few questions. Are you building a non-English image? Does your image language match your build machine? When you say that link was promising but did not solve your problem, did you find any discrepancies between the list of anchored items and SysgenSettings.out? Have you tried un-anchoring .NET/CF?
    You are not authorized to post a reply.

    Forums Board Support Packages (BSP) Windows CE