Platform Builder for Microsoft Windows CE 5.0 (cepb)

I'm using this code for run in Windows CE 4.2,----------> syscmd(
'cepb C:\WINCE500\PBWorkspaces\ShingleSprings\ShingleSprings.pbxml /MAKE
"ShingleSprings - CEPC: X86_Release" /REBUILD')

There is no error there But it have error when I use the same code in
Microsoft Windows CE5.0.

What the command code i suppose to use so it can working in Windows
CE5.0. How to use that format for that code?

thank :)

Tom
Thu Feb 09 23:53:33 CST 2006

With the release of CE 5.0 Microsoft switched to a unified build system,
meaning that CEPB no longer has it's own internal build system, but rather
thinly wraps the command line build tools. This was done to eliminate
differences in the results of image builds between the command line tools
and the IDE.

As a result, you should now be using the standard command line build tools,
such as BLDDEMO.BAT, which performs all the steps needed to create a
run-time image. However, this needs to be done from within a build window
with a properly configured environement, which is not trivial. Fortunately,
Microsoft has provided tools to help simplify this.

There are several ways to open and configure a build window - you can open
one from inside PB, you can right-click on your workspace .pbxml file in
File Explorer and use the "Open Build Window" context menu option, or you
can create a shortcut from that same context menu that you can use to open
the build window. However, I am assuming you are trying to create an
automated build, and for that you'll probably want to create a batch file
that sets up the necessary environment. For this, you'll need to use a
(somewhat unfriendly) tool called PBXmlUtils.

The command line syntax for PBXmlUtils is documented in the PB help as:
pbxmlutils /getbuildenv /workspace "%_WINCEROOT%\PBWorkspaces\<OS design
name>.pbxml" /config "<BSP>: <Target device>" > SetEnv.bat

As you can see, it's rather similar to the cepb command line syntax for your
old 4.2 build. If you run PBXmlUtils from a build window (opened using one
of the aforementioned methods), you can make use of the environment
variables to simplify the command line somewhat. For example:

pbxmlutils /getbuildenv /workspace "%PBWORKSPACE% /config "CEPC :
x86_Release" > SetEnv.bat

You can now use the resulting batch file to properly configure your build
environment for your workspace. You can also append the BLDDEMO command or
some combination of the other CE command line build tools as desired to
create an automated build script.

BTW, if you create your SetEnv batch file inside your workspace release
directory, be sure to move it somewhere else so that it doesn't get erased
during the next buildrel.

This topic has been covered previously in the CE newsgroups, so if you want
more info you may want to search the group archives and read the pertinent
posts.

Tom Gensel (eMVP)