[SERVER-17919] Add support for emitting a compilation database from SCons Created: 07/Apr/15 Updated: 19/Sep/15 Resolved: 13/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.2 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platform 2 04/24/15 |
| Participants: |
| Description |
|
Some build systems like Ninja offer support for emitting a compilation database (see http://clang.llvm.org/docs/JSONCompilationDatabase.html), which can be consumed by clang tools like clang-modernize and clang-tidy. We currently cannot easily use these tools because we cannot produce a compilation database. We should write a scons tool that lets us emit a compilation database. Producing the database should not require actually compiling any files. |
| Comments |
| Comment by Githook User [ 13/Apr/15 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |