> Try changing eval to info This introspection approach will not work in the moment when I stumble on the mentioned error messages.
> and then inspect the output to see if it makes sense as a makefile. The result should become components for recipes in my use case. > 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 I can also try this approach once more. > 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. I hope that there are more experienced software developers around who can spot programming mistakes within make statements eventually a bit easier than me. > Simplifying the example will help you and help us help you too. :) Should I explain the involved design patterns a bit more so that a common understanding can be achieved easier? Regards, Markus _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
