[comp.windows.x] diskspace woes.

martin@CITI.UMICH.EDU (11/30/88)

If I had to deal with a small disk the obvious trade off would be to remove
all .o'a directly after they have been loaded or archived.  This can be done
with not very much hastle using a trusty text editor (emacs) and the
util/imake.includes directory.

In the file Imake.tmpl (You would have to ignore the comments about don't
change this or the other)

#define NoDiskHog YES
or
#define NoDiskHog NO (if you are a diskhog)


Then you will have to cut the file Imake.rules to pieces so that after a LOAD
or ARCHIVE command has been executed a command such as "rm -f *.o *.bak" is
executed.  This way the compile takes up considerably less space.

Here is a sample change to the SingleProgramTarget macro/rule.

#if NoDiskHog
#define	SingleProgramTarget(program,objects,locallibs,syslibs)		@@\
program: objects locallibs						@@\
	$(RM) $@							@@\
	$(CC) -o $@ objects locallibs $(LDFLAGS) syslibs $(SYSLAST_LIBRARIES)@@\
	$(RM) objects							@@\
									@@\
...
#else 
#define	SingleProgramTarget(program,objects,locallibs,syslibs)		@@\
program: objects locallibs						@@\
	$(RM) $@							@@\
	$(CC) -o $@ objects locallibs $(LDFLAGS) syslibs $(SYSLAST_LIBRARIES)@@\
									@@\
...


Well this is kind of crude, but then again so is worrying about disk space all
day.  You will have to put something in the Imakefile of ./fonts/mkfontdir/ to
the effect that NoDiskHog is NO (for that directory) (Cuz there are .o's there
which are used more than once.)

You can even su to root and install the new binarys and make clean in the same
manner!