[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Building extension modules
- From: Adrián Pérez <copylight@...>
- Date: Sun, 12 Dec 2004 23:57:09 +0100
El 12/12/2004, a las 22:22, Asko Kauppi escribió:
Hmm.. I'm still not (very) convinced that this is a vital thing, but..
have you considered Hamster for the build-modules-from-scratch thing?
Maybe off-topic: would it be difficult add dependency-tracking to
Hamster? (I haven't checked Hamster code myself). i.e: if I touch
"foo.c", only "foo.o" (and other targets that might depend on them)
should be re-created. A quasi-portable way of doing that check is using
# Shell script snippet (note: "-nt" == "newer than")
if test foo.c -nt foo.o
gcc -c -o foo.o foo.c
The MacOS X man page for "test" says that its implementation is
POSIX-compliant (the same goes for OpenBSD and Linux).
Maybe newer-than-checks might be done only when the "test" utility is
installed, and the current behaviour of Hamster when not?
Currently that little point forces me to use GNU make, because
dependency-tracking is vital for build-check-fix cycles in large
Description: Mensaje firmado digitalmente