Bug 2822 – add "make clean" option to generated Makefile

Bug 2822 - add "make clean" option to generated Makefile

Summary:

add "make clean" option to generated Makefile

Status:	RESOLVED FIXED

Product:	Installation
Component:	Install
Version:	unspecified
Platform:	All All

Importance:	P3 trivial
Target Milestone:	---
Assigned To:	Charles Bacon

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-02-27 10:20 by Robert E. Parrott
Modified:	2005-03-03 12:34 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Robert E. Parrott 2005-02-27 10:20:26

After an aborted install where there was a typo in my $GLOBUS_LOCATION, trying
to reconfigure and 
remake didn't work, because the gpt tools were already setup, and the gpt-stamp
file in place, but the 
tools were in the wrong directory, which had been removed. Trying a "make
clean" was my first guess, 
but the target didn't exist.

Afer poking around and removing everything older than the initial extraction, I
found that removing 
gpt-stamp file caused gpt to be built again.

Thus, adding a "clean" stanza to the Makefile that removes this file will save
others the trouble, and be 
more in keeping with the "./configure ; make make make install " paradigm. The
stanza should just 
remove gpt-stamp and the compiled code.

Similarly, a "distclean" stanza should "clean" then remove config.status,
Makefile, etc.

------- Comment #1 From Charles Bacon 2005-03-03 12:34:02 -------

Added clean and distclean targets.

clean just removes gpt-stamp.
distclean removes config.log config.status and Makefile additionally.

Because this isn't really a recursive Makefile setup, distclean does not clean
up build artifacts in subdirectories.  However, GPT runs "make distclean" in
target subdirectories as the first step of its builds, so that shouldn't be a
problem.