Re: vcbuild usage questions
- From: "Arnaud Debaene" <adebaene@xxxxxxxxxxxxxxxx>
- Date: Tue, 1 Aug 2006 19:46:55 +0200
<jpetrang@xxxxxxxxxx> a écrit dans le message de news:
1154380606.353719.273830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I found one old post in an MSDN forum for Visual C++ that said in order
to build a particular project within a solution, I would use syntax
like this:
vcbuild ProjectName.vcproj "Release|Win32"
But when I look up vcproj in the help files, I find a note saying
vcproj files are not compatible with nmake!! At first I interpreted
that to mean that the above line is invalid from within an nmake
makefile. Since then I've read that nmake knows nothing about .vcproj
files, which means I "can't get nmake to invoke vcbuild only when the
project actually needs to be built, as the dependency information
doesn't exist in a form that nmake can understand". [Thanks, Carl
Daniels.]
So I am still a bit confused... what good is nmake if I can't use it to
build the project? What is it used for? Can I use that above line in an
nmake makefile to build the ProjectName project?
My goal is to have an automated build environment where I can check out
the source files from version control, type "nmake MyApp", and then the
app's executable will be generated.
vcbuild will itself take care of dependencies, so.... Is that so much of a
problem to type directly "vcbuild ProjectName.vcproj "Release|Win32""
instead of typing "nmake MyApp" on the command line? (if that is too much
typing, put it in a .bat file)
Arnaud
MVP - VC
.
- References:
- vcbuild usage questions
- From: jpetrang
- vcbuild usage questions
- Prev by Date: Re: best solution for detecting network devices
- Next by Date: Re: Email attachment
- Previous by thread: Re: vcbuild usage questions
- Next by thread: Dll question
- Index(es):
Relevant Pages
|