Skip to content
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

Compile_commands.json #18

Open
ddavidebor opened this issue Mar 4, 2022 · 2 comments
Open

Compile_commands.json #18

ddavidebor opened this issue Mar 4, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@ddavidebor
Copy link

ddavidebor commented Mar 4, 2022

Is your feature request related to a problem? Please describe.
I'm having issue setting up Emerge to analyze Zephyr RTOS, a rather large C project.

Describe the solution you'd like
I would like Emerge to be able to read compile_commands.json files, that contain a list of all C directories, files, and compiler arguments.

@ddavidebor ddavidebor added the enhancement New feature or request label Mar 4, 2022
@glato
Copy link
Owner

glato commented Mar 7, 2022

@ddavidebor Thanks for filing this enhancement. I'd like to have a look at this in detail, but could you give me more details or point me to

  1. the project/ repository where you have the issue
  2. your current emerge configuration that you're using
  3. an example of a compile_commands.json file

so that I can better understand the issue/enhancement here?

Thanks a lot 👋.

@ddavidebor
Copy link
Author

Hi @glato ,

The project is https://github.com/zephyrproject-rtos/zephyr and zephyr-based apps. As most Cmake projects, they generate this compile_commands.json:

compile_commands.json.zip

I fiddled with the example configs, but didn't keep any of the tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants