Le 2015-07-22 23:24, Sean Ansari a écrit :
You can print the values of variables. I use something like:
$(warning here is what is in LOCAL_FILES $(LOCAL_FILES))
What you'll see when you issue make is: foo.c bar.c buzz.c
here is what is in LOCAL_FILES
Thanks Sean, but I don't want to change the Makefile, I want to get the
variables from the Make source code (see my previous answer :
http://lists.gnu.org/archive/html/help-make/2015-07/msg00006.html )
--------------------------------------------
On Wed, 7/22/15, Kenneth Adam Miller <kennethadammil...@gmail.com>
wrote:
Subject: Re: source code: src to find (target/prerequisites/recipes)
To: "Pierre Lindenbaum" <pierre.lindenb...@univ-nantes.fr>
Cc: help-make@gnu.org
Date: Wednesday, July 22, 2015, 11:14 AM
... reading the actual makefile
itself?
Did you know that you can use remake -x to get a trace of
what make is
trying to build? You can also do a dry run to see what all
make would do
with make -n.
On Wed, Jul 22, 2015 at 5:23 AM, Pierre Lindenbaum <
pierre.lindenb...@univ-nantes.fr>
wrote:
> Hi all,
> is there a simple way/place in the code of GNU make
where I can
> find/extract
> the
>
> * target
> * prerequisite(s)
> * recipe(s) ?
>
> for example in job.c / start_job_command (would it be
the right place ?) I
> whish I could `printf` all those strings.
>
> Thank you,
>
> Pierre
>
> _______________________________________________
> Help-make mailing list
> Help-make@gnu.org
> https://lists.gnu.org/mailman/listinfo/help-make
>
_______________________________________________
Help-make mailing list
Help-make@gnu.org
https://lists.gnu.org/mailman/listinfo/help-make
_______________________________________________
Help-make mailing list
Help-make@gnu.org
https://lists.gnu.org/mailman/listinfo/help-make
