With eval and call one can get confused quite easily. Try changing eval to info and then inspect the output to see if it makes sense as a makefile. Write small test makefiles that do small aspects of what you want and build them up step by step until you get the result you want when you introduce an error you will know exactly what change made it
Most of all, don't dump the full complexity of your problem on other people because makefiles are brain twisting and hard to understand even when they are simplified. Simplifying the example will help you and help us help you too. :) Regards, Tim On 18 Jan 2015 21:07, "Norbert Thiebaud" <nthieb...@gmail.com> wrote: > On Sun, Jan 18, 2015 at 6:31 AM, SF Markus Elfring > <elfr...@users.sourceforge.net> wrote: > > > > Yes. - The evaluated variable should produce shell commands for recipes. > > I try to reuse it as a subfunction. > > then use $(call -- or possibly $$(call, if you want to defer the call > to when the recipe get invoked) > not $(eval > > >> It's just _part_ of a recipe? > > > > It is a fragment for the reuse by another variable expansion. > > > > > >> Then $(eval) is the Wrong Thing. > > > > I hope not … > > hope is not relevant... $(eval) _is_ the Wrong Thing(tm) for what you > seems to want to do > > _______________________________________________ > Bug-make mailing list > Bug-make@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-make >
_______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
