Autoconf Macro Archive
ac-archive.sf.net: - Project CVS - Download
- AM Support
- C++ Support
- C Support
- Fortran Support
- Java Support
- Cross Compilation
- Installed Packages
- LaTeX Support
- archive macros
- adl's macros
- bkorb's macros
- guidod's macros
- latex's macros
- other's macros
- rleigh's macros
- obsoleted macros
- released macros
- search index
- acincludedir m4
- acinclude (tool)
- macro howto
- ax tricks
(C) 2007 guidod
If you want to contribute ...
then please don't hesitate a second! Just send the m4 source to one of the maintainers. Currently (October 2006) that is Guido Draheim (guidod:at:gmx'de) and Tom Howard (tom:at:howardfamily'id'au) for the AC-Archive at Sourceforge and Peter Simons (simons:at:cryp'to) for the Autoconf-Archive at CrypTo. (We will try to create a common mailing to replace the old firstname.lastname@example.org mailinglist in the near future.) In any case, please read the following section about the contribution format.
For one thing - I would appreciate if you could split your macros into one-per-mail, rather than sending me your whole aclocal.m4 file, because this makes the inclusion of the submission into the archive much easier for me. It also allows me to review your macro and send you some hints (if you do not want that, please notify me, I just want to be helpful).
Also, I'd like to ask you to adhere to a few formatting rules in your submissions: Every macro should start with a few comment lines, describing what exactly it tests, what results it does produce and how it may be called by potential users. After the comments, the actual m4 code follows.
In the comments, you should use a few directives to mark special contents, that is interpreted by the perl scripts which convert the m4 input to the HTML page the users will see:
Here is an example, how your submission should look like:
Macro names should always be quoted in brackets, otherwise Autoconf will break in case a macro definition is (accidently) included multiple times in a configure.in file, as the macro name would be expanded the second time the definition is parsed. Note that autoconf can warn about symbols starting with AC_ or AM_ when it does exist but has not been found. That is a nice trick, however one should rarely start naming macros with the AC_/AM_ prefix since they might coincide with names of macros from future versions from autoconf/automake and which would shadow your own macro then.
The AX_ prefix is reserved for the usage in the extra
archive repositories and it will be ensured that
only one macro of the different name exists here. Additionally,
the `acinclude` and `acincludedir` tool will recognize macros with
this prefix, warns about missing items and be able to populate an
acinclude.m4 and/or m4/* subdirectory with extra macros.