On aclocal.m4
От | Peter Eisentraut |
---|---|
Тема | On aclocal.m4 |
Дата | |
Msg-id | Pine.LNX.4.21.0006101944250.9195-100000@localhost.localdomain обсуждение исходный текст |
Ответы |
Re: On aclocal.m4
|
Список | pgsql-hackers |
Just so you know what this aclocal.m4 thing is for: When you run autoconf it looks into this file for additional macro definitions. Several ways exist to provide additional macros: write them yourself, get them from an archive site, or use the ones provided by some program like libtool. To create aclocal.m4 you run the program aclocal. This scans configure.in and looks for all the macros that are undefined. It then looks around for definitions of these macros and copies them all into aclocal.m4. "Looks around" by default means places like /usr/share/aclocal, where things like libtool and automake leave their macros. When you write macros yourself you put them into a .m4 file and stick them (in our case) into config/ and then run `aclocal -I config'. As an analogy, you could think of all the *.m4 files as .c files and aclocal.m4 as a library, where aclocal is the linker. aclocal comes with automake as does the AM_PROG_MISSING macro that configure uses now. Note that this does not mean that anyone working on configure.in needs to have automake installed, only those that are adding external macro definitions. No, this wasn't my idea, this is the standard autoconf setup. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-hackers по дате отправления: