[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible make 3.81beta2 bug / oversight: debugging complex make file
From: |
Paul D. Smith |
Subject: |
Re: Possible make 3.81beta2 bug / oversight: debugging complex make files using $(shell echo) |
Date: |
Fri, 25 Feb 2005 10:13:21 -0500 |
%% Barry Kelly <address@hidden> writes:
bk> To debug these complex makefiles, I need to see the expanded value of
bk> variables after $(call) has been used, to verify that $(eval) is in
bk> fact evaluating the correct string.
bk> The problem is that $(shell echo $(your_var_here) >> debug.txt) fails
bk> if $(your_var_here) contains newlines, which it usually will if it's
bk> designed to be $(eval)'d.
We typically recommend people use the $(warning) function to debug call
and eval. It can't write to a separate file as you're doing here, but
it's the most reliable way to manage this.
--
-------------------------------------------------------------------------------
Paul D. Smith <address@hidden> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist