-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor compiledb implementation #1230
Conversation
6c5b6af
to
7d7a085
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on my build and it works great!
Discussed at the GDExtension meeting, and we think this makes sense! But we're going to save this one to discuss again later, when we plan to have a special meeting to tackle a lot of build system issues at once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsnopek and I discussed this and looks good.
See the comment above for a suggestion.
Not sure if anyone else has this experience, but this PR has been the only way I've gotten |
7d7a085
to
68570d6
Compare
This comment enables the possibility to build the "compile_commands.json" file by only using `scons -Q compiledb`. No need to use the argument `compiledb=yes`. And when using the `compiledb=yes`, it will create a "compiled_commands.json" automatically.
68570d6
to
2d5024a
Compare
I implemented @Faless' suggestion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Cherry-picked for 4.1 in PR #1281 |
This comment enables the possibility to build the "compile_commands.json" file by only using
scons -Q compiledb
. No need to use the argumentcompiledb=yes
.And when using the
compiledb=yes
, it will create a "compiled_commands.json" automatically.