Building MsDev from the command line
The doc and usage for msdev (VC6) command line is unclear. Here are some
notes:
- The order of parameters is important. msdev however will
not complain if the order is incorrect.
- The case of the switches is not important but the name of the project
is important.
- If you want to handle the inter-project dependencies from the
command line use /NORECURSE. If you don't use /NORECURSE, the project
dependencies in the .dsp are used. However, this can result in duplicate
compilations.
- If you have specific LIB or INCLUDE directories, use /USEENV
- The "all - Win32 Debug" must have quotes around it. The string is a
single parameter to msdev is required by the command
command line parser.
- The 'all' in "all - Win32 Debug" indicates that you want to build all
Debug configurations in the .dsp. Since there is only one
project per .dsp, the one-and-only project is built. If you named a .dsw,
msdev would build all projects in the dsw.
By using this compilation method you don't have to save the .dsw or generate
and save the .mak.
Here are some sample command lines:
- If you want to build (not rebuild) a Debug version of a project:
msdev xxx.dsp /MAKE "all - Win32 Debug" /NORECURSE /USEENV
- If you want to rebuild (not build) a Debug version of a project:
msdev xxx.dsp /MAKE "all - Win32 Debug" /NORECURSE /USEENV /REBUILD
- If you want to rebuild a Release version of a project:
msdev xxx.dsp /MAKE "all - Win32 Release" /NORECURSE /USEENV /REBUILD