Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:CDT/Build/Doug"
| Line 4: | Line 4: | ||
2. Have you looked at http://clang.llvm.org/docs/JSONCompilationDatabase.html | 2. Have you looked at http://clang.llvm.org/docs/JSONCompilationDatabase.html | ||
| + | |||
| + | Quick Answers: | ||
| + | |||
| + | 1. 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. Nope but I will. | ||
Revision as of 15:38, 22 July 2015
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.
2. Have you looked at http://clang.llvm.org/docs/JSONCompilationDatabase.html
Quick Answers:
1. 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. Nope but I will.