| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
(GH issue #448)
|
|
|
|
In the end, the extra jumping through the hoops doesn't justify the extra
safety we gain. The only plausible accidental mistake is making libul{} a
dependency of ./ but then we don't prevent the same for libue{}, which also
doesn't make much sense. Though, the consequences of doing this for libul{}
could be more severe, like messed up for-install'ness. Oh, well, I guess
people will just have to pay attention (this could be a good check for the
linter we've been thinking about).
|
|
This rule picks, matches, and unmatches (if possible) a member for the
purpose of making its metadata (for example, library's poptions, if
it's one of the cc libraries) available.
|
|
Instead of overriding this function, derived targets must now set the
dynamic_type variable to their static_type in their constructor body.
|
|
A rule hint is a target attribute, for example:
[rule_hint=cxx] exe{hello}: c{hello}
Rule hints can be used to resolve ambiguity when multiple rules match the same
target as well as to override an unambiguous match.
|
|
|
|
|
|
We were trying to be clever but GCC 10's IPA-SRA optimization didn't like it.
|
|
|
|
|
|
|
