Link to home
Start Free TrialLog in
Avatar of yoshi78
yoshi78

asked on

autobuild script

Hi,

I've been working on this for a while, but I just need a website preferably, or a book, that has a different take on what i'm doing.  Must be command line(script) driven and not COM.  The build need only perform with C/C++ files and the update of .rc files has already taken place.

I've looked on MSDN and they have plenty of stuff, but it appears to be updated for .net, I'm working with 6.0 with source downloaded from VSS already.

Thanks for the Input.
Yoshi
ASKER CERTIFIED SOLUTION
Avatar of Zoppo
Zoppo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of yoshi78
yoshi78

ASKER

ok that's where i've been at for a while.  i've can get the files from the command line but i can't spin off the make file.  But, one of the options I want is to do a partial build of a project or mutiple projects via batch file and for our purposes just make Visual source safe invisible. Keep in mind I have a nice search and explorer type windows to get to any of the files i need via program design.  I just need information on the build outside of the VSS scheme of things.

Thanks again and hope this clears it up.
>i've can get the files from the command line but i can't
>spin off the make file.
Hm ... I'm not sure if I understand it correctly

do you have problems running the 'nmake' or problems exporting
the make file?

In first case maybe you need to run 'Vcvars32.bat' before
starting the make.

ZOPPO
Avatar of yoshi78

ASKER

okay, this has to be a fluid event without VSS's help in the build area.  So pretend it's not there and you just have the tree of files that came from the repository.  You know where this tree is and can select it or subtrees or multiple trees for link and build.  I need something to do the build with the C++ compiler running in a batch file so I can call it from a program designed to automate the build process. I have one way to do it allready but I'm looking for a better way.
I still can't see the problem ... using the 'nmake' in a batch file
is quite simple ... please describe why this is not suitable
for you.
Avatar of yoshi78

ASKER

ok sorry, that was my ignorance of nmake you said

you can create a makefile with VS 'Project->Export Makefile'.
With this you can call
> nmake /f YourMakeFile.mak CFG=<Target>
where <Target> is the VS project configuration, i.e.
'YourMakeFile - Win32 Debug'.

i understand that nmake can be run from the command line.  I also understand that a makefile can be spawned inside of visual studio.  The rest i need a little help with.

thanks for the time.
yoshi


hm ... I don't see any 'rest' here ...
if you create a batchfile like

---------------------
// REM mymake.bat
call "c:\program files\Microsoft Visual Studio\VC98\bin\vcvars32.bat
nmake /f %1 CFG=%2
---------------------

you can call it from other batch file or command line like
> mymake c:\myprojects\myapp.mak "MyApp - Win32 Release"
to start the build

What else do you need?

ZOPPO
Avatar of yoshi78

ASKER

i guess the only other thing i need is a way to create the myapp.mak from the command line, or is that what mymake c:\myprojects\myapp.mak"..." does.  I believe this last line just examines the make file and creates a release build.

Just this last one and I'll leave you alone...:)
thanks for all the help
yoshi
Well, sorry, but I don't know a way to 'auto-generate' the
make files ... but, I even don't think there's a need to ...
as told above you can export the makefile from VS and handle
it like any other source-code file (i.e. put it to VSS) ...
with turning on (as told above) the 'Export Makefile when
saving project file'-option you ensure that any modifications
in the project are also done in the makefile(s).
Avatar of yoshi78

ASKER

this is being done for a repository of files which need to have an autobuild.  Therefore the workspaces for my customer which is in the 100s will need to have make files manually exported for all.  I was just trying to find a way around it but it looks like they may be out of luck.  Thanks for the info.  I ended up going with MAKE as the client is running win 2000.
Hi again,

sorry, but I just found out that maybe you can also use MSDEV
directly.

calling something like:

\path\to\msdev\MSDEV \path\to\projects\myproject.dsw /make "MyProject - Win32 Release"

should do it either...

ZOPPO
Avatar of yoshi78

ASKER

you can use MSDEV and here's the make file command(FYI)

msdev.exe MyProject.dsw –execute BuildProjectExport

thanks for the help!