Hi,
I know this is tangential, but:
MAKEFILE_LIST itself is a problem for non-recursive builds because it
gets very big if you have a lot of include statements (as opposed to a
gigantic single makefile file).
Regards,
Tim
On 8 February 2012 18:30, David Boyce invalid.nore...@gnu.org wrote:
On Thu, Feb 9, 2012 at 5:33 AM, Tim Murphy tnmur...@gmail.com wrote:
Hi,
I know this is tangential, but:
MAKEFILE_LIST itself is a problem for non-recursive builds because it
gets very big if you have a lot of include statements (as opposed to a
gigantic single makefile file).
True, but
URL:
http://savannah.gnu.org/bugs/?35493
Summary: Provide access to existing platform type data via a
builtin variable
Project: make
Submitted by: boyski
Submitted on: Thu 09 Feb 2012 05:08:57 PM GMT
Severity: 3 - Normal
That resetting MAKEFILE_LIST trick is the thing is what works for us
- I should have said that's what we had to do (although more crudely)
instead of making you write out the solution :-). I just have this
feeling that it's a bit of a sharp corner in make when doing
non-recursive makefiles and I
Follow-up Comment #1, bug #35485 (project make):
T Murphy says:
I think that getting the directory of the current makefile is useful although
I am sure my team have had trouble with $(abspath) and the way it works in
some situations on windows (unfortunately our stuff has to work on both) - it
