Skip to content

Compilation database should be generated earlier #134

Description

@TheRustifyer

Refactor

The compilation_database (compile_commands.json) is generated (if necessary) at the very end of the process.

Working with Zero I faced several times where I moved around files, and my neovim setup was unaware of the changes, so it was a total mess of errors and warnings raised by the LSP client.

It would be fine that the compilation database was (re)generated after the generate_commands procedure, and even further, to have a dedicated CLI arg that stands for such purpose, which implies to (re)generate the commands and (re)generate the compilation database, so users can update such entity without running full processes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions