RE: Targets which dont check for includes...

From:

Shah Bijal

Subject:

RE: Targets which dont check for includes...

Date:

Thu, 29 May 2003 08:10:10 +0100

This is pretty much what I need to do when I am working with dependency files
as if make finds a rule to make them then it will do so then clean them up. The
method you describe works (using MAKECMDGOALS) but you can end up putting an
ever increasing number of targets into the "exceptions" target list depending
on how your makefiles are structured.
However, there is potentially a better way, which I have been experimenting
with and which seems to work very nicely - its documented on Paul's own page:
http://make.paulandlesley.org/autodep.html
Incidently, that page contains a mine of information for makefile writers.
Regards,
Beej
-----Original Message-----
From: Paul D. Smith [mailto:address@hidden
Sent: 28 May 2003 22:40
To: Jim Kogler
Cc: address@hidden
Subject: Re: Targets which dont check for includes...
%% Jim Kogler <address@hidden> writes:
jk> Is there a way to check what target was specified? something like...
jk> if target != scour
jk> -include $$(1)_depfiles
jk> endif
Look at the MAKECMDGOALS variable (see the GNU make manual).
--
-------------------------------------------------------------------------------
Paul D. Smith <address@hidden> Find some GNU make tips at:
http://www.gnu.orghttp://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
_______________________________________________
Help-make mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/help-make
--
This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender.
Any use not in accordance with its purpose, any dissemination or disclosure,
either whole or partial, is prohibited except formal approval.
The E-Mail transmission can not guarantee the integrity of this message.
CANAL+TECHNOLOGIES will not therefore be liable for the message if modified.