#1
|
|||
|
|||
VBP builds different configs than IDE by default
I am trying to emulate a bat-file based build process using VBP. I ran across a difference between VBP and the IDE regarding building a project where no configuration is specified (a "default" configuration). The VBP GUI does not seem to allow for a "default" configuration to be built.
E.G.: When a bat-file containing this IDE command runs: Msdev c:\build\foo\foo.dsw /MAKE /REBUILD only the "Win32 Release" configuration is built. But when I build the same project using VBP, VBP tries to build many configurations. The .bld file used to build the project looks like this: <?xml version='1.0'?> <project version='5'> <step action='Make VC6' type='0'> <Attr type='11'>-1</Attr> <FileVer type='11'>-1</FileVer> <Filename>c:\build\foo\foo.dsw</Filename> <Version>1.2.3</Version> <VersionSel type='3'>2</VersionSel> <ignorefail type='11'>-1</ignorefail> <indent type='3'>2</indent> <name>VC6 build</name> </step> </project> Can I make VBP build the same *default* configuration as the IDE would? |
#2
|
|||
|
|||
No. The "default" configuration is a nebulous thing (IIRC, it might be the first configuration physically found in the .dsp file, but I don't believe it's documented anywhere and doubt it's guaranteed to work the same for all versions of Visual Studio). We don't like to rely on such questionable defaults; if you don't explicitly specify the configuration in a Make VC6 action, all configurations will be built.
|
|
|