Top-level .mak file for Visual Studio?

I inherited the Visual C ++ source body, which consists of about a dozen subprojects. One is an empty MakeAll project that depends on everyone else, so I can build the entire project by setting the active MakeAll project and choosing Build All.

I would like to automate this process and from a linux environment my instinct was to create a Makefile and build from the command line. The IDE will generate files .mak

for each of the subprojects, but not for the top-level MakeAll. (I assume this is because it has nothing but dependencies.)

The linux answer would be a Makefile that just descends into each of the subprojects and executes make

in each of them. But a quick look at the files .mak

revealed that everyone wants to tell which of several configurations to use - and apparently some use Debug, some use Release, and some use developer-generated configurations.

What is an acceptable way to create such a set from the command line?

Thank!

0


source to share


1 answer


You don't need to use make - if you have everything as solution files (.sln), then you can automate the build using the msbuild tool :

msbuild solution.sln

      



Also, why do you have a "MakeAll" project? Visual Studio doesn't require this kind of hacking, just do "build all" and it will build all the satisfying dependencies just like the typical "do all" rule.

+1


source







All Articles