Mike wrote:
> > I think you can create a dummy VC++ project that makes
> > nothing but post-compile step, and make it depends on every
> > other project in your solution. So, when you build solution,
> > the last project to be built would be that VC++ and the
> > post-compile step would copy the files you want where you want.
> >
> > Just an idea, I haven't tried this but I recall reading
> > something about this somewhere.
>
> I have used dummy VC++ projects as described to take advantage of the
> build actions, and it definitely works. It's a bit of a kludge, but
> sometimes things require a "creative" solution. :)
>
> - Mike
Using a dummy VC++ project would work but only in as far as
automation goes. I think I'd rather just execute the
batch file I wrote manually as per Fernando P. Nájera's
suggestion, and keep the projects as simple as possible.
Just make a Bin directory along side the Debug and Release
folder in the Setup project folder. Make sure that 'Bin' is
versioned and 'Debug and Release' folders are ignored.
The '/D' option in the xcopy command guarentees that only the
newest binaries get copied to the Bin directory in the event
that you want to commit the newest binary whether they be in
Debug or Release.
----------- Cut Here ---------------
@echo off
echo ---- Copy new debug files.
xcopy Debug\* Bin /D /R /C /Y
echo.
echo ---- Copy new release files.
xcopy Release\* Bin /D /R /C /Y
echo.
Pause
----------- Cut Here ---------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jul 26 19:12:21 2005