Remove spurious -g causing excess rebuilds when building alr
#1454
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Passing
-g
to gprbuild via theBuilder
package resulted in-g
being passed to all dependencies, which in turn causedalr build
to always rebuild some dependencies because they saw different switches when compiled by themselves and in the context ofalr.gpr
.We can always force a full debug build if wanted by adding
-g
to gprbuild, so removing this fromalr.gpr
to get rid of those rebuilds is preferable. Also, Alire itself is always build with-g
(via theCompiler
package inalire_common.gpr
), so this removal changes nothing in Alire's regard.