Do you understand how autotools works?
Just curious. Poll should be attached.
|
Those three who "can hack all the config files and write [their] own macros" are either boisterously optimistic -- or should share their secrets! Autotools is scary.
|
I tried to read up on it once, but before I got to a point where I could actually use it I came to the conclusion that "the cure was worse than the disease". Makefiles may have their limitations, but at least they're understandable (for the most part).
|
Quote:
|
Quote:
|
They are way above the human understanding... (at least my understanding)
Random note: as a hobby, I compile open source software on AIX, it's quite common that I have to hack configure scripts (not that I actually understand them), for example: Code:
find . -name configure -o -name config.rpath |\ |
There really needs to be a choice between 1 and 2. "haven't the foggest" does NOT describe me. I read through portions of the scripts to see what's going on. I've even improved my bash scripting skill be seeing the tricks they use. Though it's still very daunting.
Quote:
|
I once stumbled on the following overview how all files are connected with each other and I found it really helpful.
http://www.adp-gmbh.ch/misc/tools/co...iles_used.html |
Quote:
I think a lot of people forget that the main purpose of autotools is to offload the work involved in allowing for a multitude of targets within the build system. The majority of what autotools does is customize makefiles to account for what's on the system you're compiling on. And, aside from what's inherently required for the build (e.g. compiler, linker, headers,) it really only needs a bourne shell and GNU make. Kevin Barry |
Quote:
|
and m4, and libtool.
The actual autotools API is pretty straight-forward, and writing an auto tools check macro in m4 is not terribly difficult. The question is - do you really need such a hammer? |
the configure scripts do *not* need m4, libtool, perl, autoconf or automake. Only when *generating* autotools files are these needed.
|
Quote:
I've had configure scripts included with projects FAIL TO EXECUTE for a variety of reasons, requiring that I rerun autoreconf -i to regenerate a configure script. OR there's always the case where the project doesn't include a ./configure (gaim's CVS repository about 10 years back was this way). The advantage of autotools has less to do with the configure script itself as it has to do with the massive infrastructure used to generate that script. In those cases, you MUST have the full autotools environment or you can't even TRY to hack together a makefile that will work. |
Quote:
Kevin Barry |
I'd put it in the category of 'I really should learn this, now that I've seen what it does.' Kind of like emacs or Eclipse.
--- rod. |
All times are GMT -5. The time now is 09:43 AM. |