Skip to content

Always rebuilding even though there are no changes. #8210

@tejlmand

Description

@tejlmand

Hi,

I have noticed that when running ninja, there is always something to rebuild / the project is out-of-date.
The reason for this is the generation of syscalls.json.

To me it seems that what is trying to be achived is to re-run parse_syscalls.py whenever a header file is added/removed/updated in ${PROJECT_SOURCE_DIR}/include

Therefore the add_custom_command depends on the always_rebuild target.
My suggestion is to make parse_syscalls.py depend on the folder (works in Linux both whenever a file is modified/added/removed).
On windows each header must be monitored, as well as the folder.

This way, the always_rebuild can be removed.
Currently only parse_syscalls.py depends on always_rebuild, and the reason I suggest removing that target, is to not tempt others to use it, if they can find a way to avoid.
Keeping always_rebuild might make someone choose the easy path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions