Autoconf Macro Archive - Project CVS - Download
Macro Index
- AM Support
- C++ Support
- C Support
- Fortran Support
- Java Support
- Cross Compilation
- Installed Packages
- Miscellaneous
- LaTeX Support
- Uncategorized
- 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

- Contribute!
- History
- acincludedir m4
- acinclude (tool)
- macro howto
- ax tricks
- maintainers
- License
- Topics


(C) 2007 guidod

AC Archive Maintainers

The is a community project - there is not just one maintainer. Anyone might apply to help with maintanance of the macro set and (web) pages being built. The complete sources of this website are available in a tarball that you can use locally to test the functionality or to create an in-house local ac-macro repository. If you want to help then you should first subscribe to the mailing list of this project at

become a sourceforge project member

To become a project member you do need to get first a sourceforge user account. The biggest problem here is to get a meaningful account name as there are already so many sourceforge users. -

Next ask one of the existing admins of the ac-archive to add your name (the unix name!) to the project and adding some write permissions. If you have been a respected participant of autoconf developments then you might be rocketed into the admin position from the beginning. - The admin shall use (a) My Page >> summary >> My Projects / Autoconf Macro Archive >> Admin >> Members >> [Add a developer to this project] (b) [on the members settings page] Set Project Role and allow access to the Web Space and allow access to the CVS Repository.

The last part is in getting a writeable cvs checkout trunk. This is a bit tricky if you are new to sourceforge. You need to setup SSH with a valid key pair - copy-n-paste the public key (*.pub) to your user account "host access information" {{ My Page >> summary >> Account Options >> [Scroll down] [Edit SSH Keys for Shell/CVS]. }} and wait about 4 hours for the system to push the ssh key into the appropriate places. When completed you can follow the instructions to get a "Developer CVS Access via SSH" on the project CVS mainpage at .

basic maintanance work

In the CVS checkout (either anonymous or in developer role) you can simply type `make` to rebuild the html webpages. It does require GNU Make and Python and english aspell (tested in a Linux system). The generated pages are not put next to the source files - the "_htdocs" subdirectory is the root of all the files that shall be visible at later. You can point your browser to this local place to have an eyeball check if everything is okay.

In order to put the generated pages onto you just need to type `make install-sf`. However, that includes a tarball of unix manual pages which are created via an intermediate "ac-archive-macros.docbook" master given to Tim Waugh's "xmlto" wrapper around Norman Walsh's "docbook-xsl-stylesheets" and xslt-proc from Daniel Veillard's "libxslt". These are standard tools shipped with all modern Linux distros but better check for them first and try `make man7` for a test.

Adding or modifying an */*m4 macro should be detected in the GNUmakefile automatically. An additional task here is to update the "ac-archive" subdirectory from the source running `make latest`. When done, run `cvs -n commit` to see what files have changed and add/commit them to the CVS sourceforge repository.

Adding or modifying a doc/*.htm page should be detected in the GNUmakefile automatically. When adding a new page you should add it to the navigation bar visible on the left side at - you can do that by modifying "ac_archive/" (scroll down near the end).

Current Maintainers

After doing a change, don't forget to add a comment to the ChangeLog and commit everything back to the cvs with a meaningful comment.

  • The admins are...
  • Guido Draheim (sourceforge account "guidod")
  • Tom Howard (sourceforge account "tomhoward")