Hi,
That's well understood and the problem at the moment is that $(info)
statements etc are executed and "pollute" the output.
It does point out an area of scalability though because in our testing
it made an immense difference. Some of our macros are perhaps 50k
(effectively although that's re
Hi,
In one of my projects I've written a small make script which includes given
makefiles and then prints out valid make code with definitions of all new
variables found in the included makefiles (based on the value of
$(.VARIABLES)).
You can see the source code of the script here:
http://code.go
On Sat, 2012-02-18 at 18:46 +, Tim Murphy wrote:
> The option you need is:
> -p, --print-data-base Print make's internal database.
This is the (only) place to start but just to warn you: the output of
this option was not designed to be used this way and we don't guarantee
that the format
Hi,
This can be done and we have tried something similar for exactly the
same reasons.
It wasn´t utterly trivial for us for a number of reasons but in your
case you might not have the same problems. We were trying to
pre-parse the makefile in parallel then read the parsed version.
We didn try t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello list,
The short version
Is there any way to make make dump it's database to a makefile and
then reuse that dumped makefile to build the source?
The long version
In one of our projects at work, we use a rather complex set of
macros[1] to make
