Re: Custom Build Command, CEC entry, or BIB file?

From: Joseph Garibaldi (jsph_garibaldi_at_yahoo.com)
Date: 10/06/04 

Date: Wed, 6 Oct 2004 21:07:47 +0530

yep..setting wincerel=1 either by opening a command window and building it
there.....or by setting it in the environment variables tab of PB and then
doing a feature build, copies the built binary into the release directory as
well. 

-- 
cheers,
Joseph Garibaldi.
B'lore, India.
"Nick" <anonymous@tentechnologies.com> wrote in message
news:OxxT1q6qEHA.192@tk2msftngp13.phx.gbl...
> Yes, 4.2., I'm using method #2.  I don't mind using #4, I just figured out
> #2 first.
>
> I'm curious why is #1 a hack?  The only difference between #1 and #2/#3 is
> the location of the DLL (FLATRELEASE vs. some other folder).  Perhaps the
> original intent was to have everything associated with the platform in one
> folder and this breaks that assumption.  Is there a deeper darker piece I
am
> missing?  After all, 5.0 has hard links to files to decrease the need for
> copying files all over the place.  Since the path to the file is all
macros,
> this should work from one installation to another.
>
> As I was writing this I came up with another question.  Can I simply set
> WINCEREL=1 in the SOUCES file for my driver, build it, then make image
> (removing all the copy stuff per  #2)?
>
> Thanks,
> Nick.
>
>
> "Chuck Zalinski" <charlz@online.microsoft.com> wrote in message
> news:kPjB9dyqEHA.1340@cpmsftngxa06.phx.gbl...
> > I assume you are using a version prior to 5.0.
> > In 5.0 we added support for this.
> >
> > #1 is a hack. I wouldn't take this approach.
> > #2 or #3 will both work in pre 5.0, I would choose #2 because it works
for
> > both IDE builds and command line builds, and will work in 5.0 (#3 won't
> > work in 5.0)
> >
> > #4 is the cleanest way but is probably cumbersome, so I assume you were
> > trying #2 or #3 to speed things up for day-to-day development.
> >
> >
> > In 5.0 we added support for #4
> >
> > Here is what you can do (5.0):
> > * From the FileView workspace tab, select the component you want to
build,
> > right click to get the menu, and choose "Show In Favorites"
> > This puts it in your Favorites folder and makes it easy to find.
> > * Right click on this entry in favorites and choose "Make Run time image
> > after build". This is a global setting and will run makeimg after any
> build
> > * Now any time you right click on this component and select "build" you
> > will get #4 happening
> >
>
>
Loading