Thanks Paul.
Do you think it would be possible to make each signal name a special target
for a future release of gmake?
For example, I believe Ctrl-C is "SIGINT". So you could have:
.SIGINT :
@ echo "Interrupt signal received"
@ <commands to clean up launched sub jobs>
@ echo "exiting"
I'm not sure how feasible this would be within some future make, but I think
it would make a good feature.
Milan
-----Original Message-----
From: Paul D. Smith [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 12:43 PM
To: Bhatt, Milan C
Cc: '[EMAIL PROTECTED]'
Subject: Re: GMAKE signal handling
%% "Bhatt, Milan C" <[EMAIL PROTECTED]> writes:
bmc> I know this may be a long shot, but has anyone found some way for
bmc> GMAKE to handle signals? Specifically, I would like to capture
bmc> the Ctrl-C interrupt signal and have GMAKE execute some commands
bmc> before exiting.
It's simple enough to do from within the code, but there's no way to do
it from within a makefile.
--
----------------------------------------------------------------------------
---
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.paulandlesley.org/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad
Scientist
_______________________________________________
Help-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-make
