Update of bug #51338 (project make):
Status: None => Not A Bug
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #3:
Secondary expansion is a shorthand that allows you to use some automatic
variables in the prerequisites list (most commonly $@) so that you can modify
the prerequisites based on the target name. It is a simplified method to
generate make rules in a limited way, without resorting to full-fledged eval
which provides a superset of secondary expansion's capabilities. You might
consider reading (starting from the oldest and going to the newest) the set of
blog posts here: http://make.mad-scientist.net/category/metaprogramming/ which
describe ways to define make rules that have some amount of variability.
You don't need to use secondary expansion inside the recipe, because you
already have access to the automatic variables like $@ there.
In your situation you are creating entire rules using a defined template with
eval, so you have no need of secondary expansion there either: you can access
any value that was used in the target list directly (this is what Martin is
telling you).
I don't understand what you mean by "such approaches would be directly
distributed with the make software", but I don't want to use the bug tracker
to design a new feature from scratch. If you have a specific design in mind
please post it here with explicit examples and discussion of exactly how it
would work and I'll reopen this enhancement request. If you're asking for
someone else to design a new feature based on an abstract description of your
needs please use the mailing lists to discuss it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51338>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
