Source code browse
Revision:
19
(of 19)
Couple of little errors turned up in perf testing.
| Filename | Author | Revision | Modified | Log Entry |
|
|
tim.bray@sun.com
|
1
|
about 1 year ago
|
Initial check-in
|
|
|
tim.bray@sun.com
|
2
|
about 1 year ago
|
Patch to configure.ac from Jack ...
|
|
|
tim.bray@sun.com
|
2
|
about 1 year ago
|
Patch to configure.ac from Jack ...
|
|
|
tim.bray@sun.com
|
1
|
about 1 year ago
|
Initial check-in
|
|
|
tim.bray@sun.com
|
19
|
about 1 year ago
|
Couple of little errors turned u...
|
|
|
tim.bray@sun.com
|
1
|
about 1 year ago
|
Initial check-in
|
|
|
tim.bray@sun.com
|
1
|
about 1 year ago
|
Initial check-in
|
|
|
tim.bray@sun.com
|
1
|
about 1 year ago
|
Initial check-in
|
This directory contains the source code for mod_atom, an Apache module which
implements the server side of the Atom Publishing Protocol, as specified in
RFC5023.
INSTALLING
Building Apache modules can be challenging. mod_atom is particularly tricky
because it needs TidyLib for parsing and sanitizing HTML that people try to
upload.
To build mod_atom, you need an Apache installation. I have always used one that
I built from source; I do not know if this will work in other circumstances.
You also need TidyLib. If the configure script cannot find a sufficiently
modern TidyLib (one that provides a declaration of TidyAllocator), it will
try to checkout the TidyLib source code from sourceforge.net using CVS and
build it to make the necessary .o files available. Of course, this means that
you must have a CVS client and an Internet connection.
If you checked the mod_atom source code out using Subversion, then the first
step is to run:
autoreconf -vfi
This will run the autotools to generate a configure script. More information
about autoreconf is available online:
http://sources.redhat.com/automake/automake.html#Future-of-aclocal
To build mod_atom, run the configure script to generate a Makefile. The script
accepts many options; for example, to explicitly specify the path to the Apache
apxs tool, use the --with-apxs=PATH option:
./configure --with-apxs=/usr/local/apache2/bin/apxs
Without this option, the configure script will try to find the Apache apxs tool
automatically. For more information about available options, use the --help
option:
If you are about to do some serious development and might need to debug,
something like this might be appropriate:
CFLAGS=-g ./configure --with-apxs=/usr/local/apache2/bin/apxs
./configure --help
Finally, run make:
make
USING
Helpful information about using mod_atom may be found online:
http://www.tbray.org/ongoing/When/200x/2007/06/25/mod_atom
http://www.tbray.org/ongoing/When/200x/2007/09/16/Autumnal-Atom