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 08:41:03 +0530

hi guys,

    Just to clear up my understanding, would

"2. Make the file entry in the BIB file point to $(_FLATRELEASEDIR) and have
a custom build command at pre-make-image time that copies the DLL"

    be the same as having a custom build command (to copy) at the
post-feature build
phase ? Since the pre-make image time routine applies to the current
feature in the PLATFORM SETTINGS,
i guess your idea would execute properly. Is there any problems with having
them at "post-feature build" phase ?

    And, do you have any place where these different phases and their exact
differences have been documented ? 

-- 
cheers,
Joseph Garibaldi.
B'lore, India.
"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
>