You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @claudiiolima -- I'm not sure if you're asking if you can set flags for the test executable, or if you want to set flags differently for different parts of the executable? The feature you referenced changes the flags per test executable (not per file). There is only one test executable for a release, so this isn't necessary.
You CAN set the :flags: for the released executable, similar to tests:
:flags:
:release:
- --flag
- -f
If you need to be able to compile different parts of the release differently, I'm just now putting the final touches on the :dependencies plugin, which (among other things) lets you build sub-sections of your release as static libraries. These could have different settings from eachother also.
I hope this answers your question, but if I'm misunderstanding, just say the word. I'm happy to take a look at an example of what you'd like to do. :)
My idea was about per file matcher, but as you say it was changed for per executable matcher, I didn't understand it before.
But is there a change that per file matcher comes back for release build? I think it is important during development, like changing optimization only in specific files to work better at debug
You make a good point about optimization changes, etc. Thanks for the thought! I don't think it'll probably make it into the 0.32 release, but our goal is to make this the last "giant release" and have the releases MUCH more frequent after this point. :) I'll leave this issue open so we remember to tackle it!
Activity
mvandervoord commentedon Feb 26, 2024
Hi @claudiiolima -- I'm not sure if you're asking if you can set flags for the test executable, or if you want to set flags differently for different parts of the executable? The feature you referenced changes the flags per test executable (not per file). There is only one test executable for a release, so this isn't necessary.
You CAN set the
:flags:for the released executable, similar to tests:If you need to be able to compile different parts of the release differently, I'm just now putting the final touches on the
:dependenciesplugin, which (among other things) lets you build sub-sections of your release as static libraries. These could have different settings from eachother also.I hope this answers your question, but if I'm misunderstanding, just say the word. I'm happy to take a look at an example of what you'd like to do. :)
claudiiolima commentedon Feb 26, 2024
My idea was about per file matcher, but as you say it was changed for per executable matcher, I didn't understand it before.
But is there a change that per file matcher comes back for release build? I think it is important during development, like changing optimization only in specific files to work better at debug
mvandervoord commentedon Feb 26, 2024
You make a good point about optimization changes, etc. Thanks for the thought! I don't think it'll probably make it into the 0.32 release, but our goal is to make this the last "giant release" and have the releases MUCH more frequent after this point. :) I'll leave this issue open so we remember to tackle it!
[-]Flags per-matches at Release[/-][+]Flags per-file-matchers at Release[/+]