Age | Commit message (Collapse) | Author | Files | Lines |
|
Also recognize 23 in addition to 2x for C23.
|
|
|
|
|
|
It was surprising and inconvenient that they didn't end up in $<. Plus,
such prerequisites can always be marked as ad hoc explicitly.
|
|
|
|
The old order messed up the for-install signaling logic. See the long comment
in install::file_rule::apply_impl() for background and details.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Failed that we will end up with a dependency cycle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See llvm-project issue 63284 for details.
|
|
See GCC bugs 107532, 110213.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
While assigning null directly is unlikely, it's fairly easy via a variable
expansion. Real-world example:
./: exe{tensor}: include = $config.Eigen.unsupported
|
|
|
|
|
|
|
|
This makes it consistent with the existing ad hoc rules semantics.
|
|
|
|
|
|
This can be used to handle situations where the dynamic targets are placed
into subdirectories.
|
|
This allows specifying custom extension to target type mapping.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|