Paul Smith wrote:
On Thu, 2012-02-09 at 17:25 +, Tim Murphy wrote:
I also think that it can be expensive to append things onto very long
lists in make but that's just suspicion and I really need to take a
proper look at it instead of making accusations.
Appending is not very expensive. Ma
On Thu, 2012-02-09 at 17:25 +, Tim Murphy wrote:
> I also think that it can be expensive to append things onto very long
> lists in make but that's just suspicion and I really need to take a
> proper look at it instead of making accusations.
Appending is not very expensive. Make doesn't know
Follow-up Comment #2, bug #35485 (project make):
I don't think this implementation is appropriate. The value of "MFDIR" will
change wildly over time if makefiles are included which can't possibly be what
you want. For example:
.MFDIR = $(abspath $(dir $(lastword $(MAKEFILE_LIST
$(info MFDI
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
Update of bug #35525 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Fixed Release:
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
