[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #18617] Better debugging facilities: tracing rule invocation.
From: |
Darren Hiebert |
Subject: |
[bug #18617] Better debugging facilities: tracing rule invocation. |
Date: |
Thu, 04 Jan 2007 21:21:30 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 |
Follow-up Comment #1, bug #18617 (project make):
I would like to piggyback on this enhancement request. I would like to see
some manner of printing out the fully resolved makefile that make processes
after evaluating $(foreach), $(eval), and ($call) functions. For example,
consider this complicated rule, contained within a macro define:
ifdef $(1)_DELIVERY_INCLUDE
DELIVERY_INCLUDE += $$($(1)_DELIVERY_INCLUDE)
$$(foreach file,$$($(1)_DELIVERY_INCLUDE),$$(eval $$(call
delivery_include_rule),$$(file),$$($(1)_INCLUDE_DIR)$$(notdir $(file)))))
endif
Make run with -p just prints the macro define including this, but not the
actual makefile rules it expands to each time it is evaluated. I need to be
able to see what it expands to as an actual rule to see if I didn't make a
mistake somewhere. It would be great if there was a debug option to enable
this behavior.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18617>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #18617] Better debugging facilities: tracing rule invocation.,
Darren Hiebert <=