Re: QUERY: Automated CVS-VC6 building

From:

"Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam>

Newsgroups:

microsoft.public.vc.ide_general,microsoft.public.vc.language,microsoft.public.vc.project_mgt,microsoft.public.vstudio.development,microsoft.public.vstudio.general

Date:

Fri, 20 Mar 2009 19:28:07 -0700

Message-ID:

<uT3ysycqJHA.4460@TK2MSFTNGP06.phx.gbl>

Tamas Demjen wrote:

And Wan wrote:

1. Sync to a specific changelist (collection of versions) in Perforce
2. Use MS VC6 to batch build (consists of multiple projs of
dlls/exes)
and might need rebuild/relink due to dependencies.
3. Once 100% built (rebuild doesn't do any further linking) then copy
files to folder with same name as the changelist #.
4. Repeat from step 1 onto the next changelist.

FinalBuilder is another way of doing it, if you don't want to rely on
the command line and batch files:
http://www.finalbuilder.com/Products/FinalBuilder/ScreenShots/tabid/62/Default.aspx

FB has Perforce and VC6 actions built in. All you have to do is drag
and
drop the various actions needed to build, test and release your
product.
It is fully scriptable, which is a lot more powerful than what you can
do in a batch file. You can even put a breakpoint and debug your build
process.

This convenience will cost you a little money, but it may be well
worth
it if your build process is fairly complicated.

I'll second the recommendation of FinalBuilder - I use it for all of my
product builds. You can do it all with batch files, Perl, Python, etc (been
there, done that), but using FB is far more pleasant. The pre-built support
for dozens (if not 100s) of tools and Windows features is well worth the
price.

-cd