[SERVER-25533] The compiledb targets for scons produces an empty file Created: 10/Aug/16 Updated: 05/Apr/17 Resolved: 13/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | scons compiledb output: |
| Sprint: | Platforms 2017-01-23, Platforms 2017-02-13 |
| Participants: |
| Description |
|
3.2 produces a compile_commands.json file useful for external tooling when scons compiledb is invoked. Current master now produces an empty file. |
| Comments |
| Comment by Mira Carey [ 13/Feb/17 ] |
|
Tried it on master, produces a perfectly good compilation database. I guess whatever I had going on isn't a problem anymore |
| Comment by Andrew Morrow (Inactive) [ 17/Oct/16 ] |
|
I just tried this on both my OS X machine and my Ubuntu 16.04 machine, and I get a populated file on each. In both cases, I was using the vendored copy of SCons 2.5.0 that is in our tree. Can you try using that (via buildscripts/scons.py) and see if it works for you? |