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

Compilation database generation caveats #628

Closed
sim642 opened this issue Mar 8, 2022 · 1 comment
Closed

Compilation database generation caveats #628

sim642 opened this issue Mar 8, 2022 · 1 comment
Assignees
Labels
Milestone

Comments

@sim642
Copy link
Member

sim642 commented Mar 8, 2022

This issue serves as a WIP place to collect issues and workarounds for different compilation database generators we have encounted.

compiledb

  1. Doesn't properly escape -D argument values (Tmux bench#8 (comment), Other attempted projects bench#14 (comment)).
  2. Errors with .deps and Makefile targets (chrony bench#17).
    • Workaround is to remove the manually.
  3. Assumes English locale (GobCon 23.02.2022 notes).
  4. Doesn't completely decompose multi-file targets (Compilation Database: Support for entries with multiple .c files in one command #624 (comment)).
  5. Uses relative paths for preprocessing and thus in AST.

bear

  1. Bear 2.3.11 from Ubuntu 18.04 produces incomplete database (OpenSSL bench#7 (comment), OpenSSL bench#7 (comment)).
    • Bear 3.0.8 seems fine.
@michael-schwarz
Copy link
Member

Would it make sense to move this to some more permanent place (e.g. in the documentation) rather than an issue?

(An issue implies that it can at some point be resolved, which does not seem to be the case here).

@sim642 sim642 self-assigned this Nov 21, 2022
@sim642 sim642 closed this as completed in e1bc675 Dec 5, 2022
@sim642 sim642 added this to the v2.2.0 milestone Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants