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

Support for per-file flags #482

Open
flit opened this issue Mar 10, 2021 · 3 comments
Open

Support for per-file flags #482

flit opened this issue Mar 10, 2021 · 3 comments

Comments

@flit
Copy link
Contributor

flit commented Mar 10, 2021

Some projects require per-file compiler flags.

This should probably work by allowing a source file entry to be a usual settings dict.

@0xc0170
Copy link
Member

0xc0170 commented Mar 14, 2021

I recall working on some projects that had specific files settings. I always wanted to avoid this (it is hidden from common settings).

The support for all tools will take the most effort.

@flit
Copy link
Contributor Author

flit commented Mar 14, 2021

Yeah, it's a pain. Unfortunately it's needed for some things I'm working on in Research. Currently I'm working around it with a new tool-specific custom_rules setting added in my fork. It accepts a string that is just copied directly into the generated Makefile or CMakeLists.txt.

@eleenest
Copy link

Just curious if this feature is still in the works.

Not urgent, but we did have a case where we wanted to apply flags to only some files (i.e. enable -Werror for files that have been cleaned up, so they stay clean).

Eric

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

No branches or pull requests

3 participants