Hi,
I am working on wiince 5.0 build system.In my build enviorment
i have seen when i run baseosenv.bat (in command prompt) then WINCEREL
will be set to 1.So after that if i change the WINCEREL = nothing then
also i observed that blddemo.bat is calling buildrel and after that
makeimg.Actually i dont want to do at a stretch buildrel and makeimg
during calling of blddemo clean -q or blddemo -qbsp. I want to do
buildrel and makeimg manually through command prompt.blddemo -norel
option is there but i canot call that beacuse for that i have to
modify some other batch file and i canot do that .But i can change the
enviormnet setting so is there anyway stop to call buildrel and
makeimg during calling blddemo.bat ?


Your inputs are most welcome

Thanks
Chinmoy

Re: buildrel solution by Silver

Silver
Sun Aug 19 19:21:11 CDT 2007

WINCEREL causes targets to be copied to the release directory as they are
built. It does not stop blddemo calling buildrel.

What are you actaully attempt to achieve? Feel free to use the command
prompt for all of your building, it is perfectly fine for many (most?) it is
where we do almost all of our builds.

You can build with a custom build command in the IDE, and add in any command
that you feel like.

Geoff
--


Re: buildrel solution by Bruce

Bruce
Mon Aug 20 16:57:18 CDT 2007

Did you look at blddemo.bat? The answers to your questions are there.

Just before running buildrel it looks to see if _BLDDEMO_NOREL is set.
before running makeimg it looks to see if _BLDDEMO_NOMAKEIMG is set. I will
leave it to you to look in blddemo.bat to see how those get set.

HINT: The check boxes in the Build OS menu are used to control these.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

<chinmoy.chittaranjan@gmail.com> wrote in message
news:1187544760.883292.142850@q3g2000prf.googlegroups.com...
> Hi,
> I am working on wiince 5.0 build system.In my build enviorment
> i have seen when i run baseosenv.bat (in command prompt) then WINCEREL
> will be set to 1.So after that if i change the WINCEREL = nothing then
> also i observed that blddemo.bat is calling buildrel and after that
> makeimg.Actually i dont want to do at a stretch buildrel and makeimg
> during calling of blddemo clean -q or blddemo -qbsp. I want to do
> buildrel and makeimg manually through command prompt.blddemo -norel
> option is there but i canot call that beacuse for that i have to
> modify some other batch file and i canot do that .But i can change the
> enviormnet setting so is there anyway stop to call buildrel and
> makeimg during calling blddemo.bat ?
>
>
> Your inputs are most welcome
>
> Thanks
> Chinmoy
>



Re: buildrel solution by Arnie

Arnie
Mon Aug 20 17:05:46 CDT 2007

Depending on how much control you want you can create your own command-line
tool to handle various build flavors.

The pbxmlutils.exe tool is a start in this direction.

You can also go directly to the build automation level by using the
microsoft.platform.common assembly (it contains all the funcationality that
PB or pbxmlutils eventually use). This assembly abstracts all the
common/core functionality of PB in a simple interface.

Although this is probably overkill for what you want I thought I'd pass
along the the ability for ultimate control.

You can see the wince base blog site for some samples of
microsoft.platform.common in use.

-arnie

"Silver" <moc.liamtoh@gnirrevliseht> wrote in message
news:%23AXaHAs4HHA.5724@TK2MSFTNGP05.phx.gbl...
> WINCEREL causes targets to be copied to the release directory as they are
> built. It does not stop blddemo calling buildrel.
>
> What are you actaully attempt to achieve? Feel free to use the command
> prompt for all of your building, it is perfectly fine for many (most?) it
> is where we do almost all of our builds.
>
> You can build with a custom build command in the IDE, and add in any
> command that you feel like.
>
> Geoff
> --
>