[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: source code: src to find (target/prerequisites/recipes)
From: |
Sean Ansari |
Subject: |
Re: source code: src to find (target/prerequisites/recipes) |
Date: |
Wed, 22 Jul 2015 15:02:38 -0700 |
Welcome. There is also a database option. But you may have looked into that
also. Here is what the manual has:
‘-p’
‘--print-data-base’
Print the data base (rules and variable values) that results from reading the
makefiles; then execute as usual or as otherwise specified. This also prints
the version information given by the ‘-v’ switch (see below). To print the data
base without trying to remake any files, use ‘make -qp’. To print the data base
of predefined rules and variables, use ‘make -p -f /dev/null’. The data base
output contains file name and line number information for recipe and variable
definitions, so it can be a useful debugging tool in complex environments.
Hope it helps.
--------------------------------------------
On Wed, 7/22/15, Pierre LINDENBAUM <address@hidden> wrote:
Subject: Re: source code: src to find (target/prerequisites/recipes)
To: "Sean Ansari" <address@hidden>
Cc: address@hidden
Date: Wednesday, July 22, 2015, 5:54 PM
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
<address@hidden>
> wrote:
>
> Subject: Re: source code: src to find
(target/prerequisites/recipes)
> To:
"Pierre Lindenbaum" <address@hidden>
> Cc: address@hidden
> 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 <
> address@hidden>
> 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
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/help-make
> >
>
_______________________________________________
> Help-make mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/help-make
_______________________________________________
Help-make mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-make