[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: makefile improvements
From: |
John Darrington |
Subject: |
Re: makefile improvements |
Date: |
Mon, 12 Oct 2009 10:52:16 +0000 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Sun, Oct 11, 2009 at 09:36:21PM -0700, Ben Pfaff wrote:
I created a branch with improvements to the PSPP makefiles, named
"makefiles". I'd appreciate it if you'd look it over and make
comments before I merge anything into master.
1.
po_CLEAN:
@if test "$(srcdir)" != .; then \
echo rm -f $(POFILES); \
rm -f $(POFILES); \
fi
In principle this is fine, but I'm not sure that the test is very reliable.
For example if the curreent directory is /home/john and srcdir is "/home/john"
or "../john" then it'll give the wrong result. There are several other places
in the makefiles where a similar trick is used. Perhaps we should do the
test in configure, and define a conditional ??
2.
$(POFILES): $(POTFILE)
$(MSGMERGE) $(top_srcdir)/$@ $(top_srcdir)/$(POTFILE) -o $@
$(POTFILE) is a generated file, so it will be in $(top_builddir) not
$(top_srcdir).
3.
The $(VARIABLE) syntax is usually preferred, because it is possible for
the user to override it at "make" time, whereas @VARIABLE@ is hardwired at
"configure" time.
I'm in two minds about whether this is an advantage or not.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.
signature.asc
Description: Digital signature