Talk:CDT/Build/Doug

Questions from Sergey:

1. Will the new build model support building multiple binary artifacts per project? Since each GTest is a separate binary, it doesn't make sense to create a separate project for every unit test.

<Doug> Well, the trick is, there is really no build model. Whatever system you're using to build, CMake, qmake, ..., decide those limitations. Having said that, we need to make sure we deal with multiple binaries in other places like the launch bar. How do we decide which binary to use for a given launch.

2. Have you looked at http://clang.llvm.org/docs/JSONCompilationDatabase.html

<Doug> Nope but I will.

Questions from Marc-Andre:

1. I consider CMake, qmake, autotools, CDT Makefile generator to be "build generators" (build configurators?). Those typically need to be ran once than you execute a build command such as make, ninja, etc. Would it not make sense to have the build generator concept separate from the builders?

<Doug> I thought about that. CMake provides a good example of that. The parameters you pass, like "-G Ninja", decides which build command to run next. And the build generators decide what parameters you can pass to the build command. So I think during a given invocation, they are tied together. Having said that, though, I imagine we'll want to provide a class for error parsing the build output like we do with make, or something like that. We should really walk through the use cases in more detail so we can decide.