There is this annoying thing that the environment variables that are set in
the platform builder 5.0 environment (platform->settings, environment tab)
are not available to the %_TGTPLAT%.bat batch file when it gets called.
Platform builder seems to set them AFTER it has called the %_TGTPLAT%.bat
batch file.
I consider this a bug and I would like to see it get fixed.
You can simple verify what I am saying by adding this to your
%_TGTPLAT%.bat batch file: set >c:\envdump.txt. Then, set a variable
(platform->settings, environment tab, and define HELLO=1). Select Build
OS->Open Release directory. From that command shell then "type
c:\envdump.txt". You will see that HELLO is not defined. I am sorry, but I
would expect that HELLO variable to be set so that I can use it to fine tune
certain BSP configuration settings inside the %_TGTPLAT%.bat batch file ! It
is even funny that we cannot even determine inside that batch file if we are
in a debug build (%WINCEDEBUG% is set to retail even for a debug workspace,
at the time your %_TGTPLAT%.bat batch file gets called...)
NOTE:
cc: cefdbk@microsoft.com (see if this gets any reply, normally this is a
black hole where you can send all your bug reports and comments but never
ever get any reply from. This is also annoying somehow. You will report
about 10 bugs but then after no feedback from MS at all, you just stop doing
it you know, there's time better spent, like explaining the same bug or
comment to your cat or something, at least the cat thinks it is still
amusing. Anybody ever got any feedback from that e-mail address that MS
urges you to sent bug reports and comments to ?).