cvs commit: httpd-2.0/docs/manual/style/man manpag: msg#00403 apache.cvs

nd 2003/04/29 16:15:25

Modified: docs/man Tag: APACHE_2_0_BRANCH apxs.8
docs/manual/style/chm Tag: APACHE_2_0_BRANCH hhc.xsl
docs/manual/style/man Tag: APACHE_2_0_BRANCH manpage.xsl
Added: docs/manual/programs Tag: APACHE_2_0_BRANCH apxs.html.en
apxs.xml apxs.xml.meta
Removed: docs/manual/programs Tag: APACHE_2_0_BRANCH apxs.html
Log:
manpage backport.

Revision Changes Path
No revision

No revision

1.7.2.2 +241 -432 httpd-2.0/docs/man/apxs.8

Index: apxs.8
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/man/apxs.8,v
retrieving revision 1.7.2.1
retrieving revision 1.7.2.2
diff -u -r1.7.2.1 -r1.7.2.2
--- apxs.8 2 Feb 2003 20:50:05 -0000 1.7.2.1
+++ apxs.8 29 Apr 2003 23:15:24 -0000 1.7.2.2
@@ -1,458 +1,267 @@
-.TH apxs 8 "April 1998"
-.\" The Apache Software License, Version 1.1
-.\"
-.\" Copyright (c) 2000-2003 The Apache Software Foundation. All rights
-.\" reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\"
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\"
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in
-.\" the documentation and/or other materials provided with the
-.\" distribution.
-.\"
-.\" 3. The end-user documentation included with the redistribution,
-.\" if any, must include the following acknowledgment:
-.\" "This product includes software developed by the
-.\" Apache Software Foundation (http://www.apache.org/)."
-.\" Alternately, this acknowledgment may appear in the software itself,
-.\" if and wherever such third-party acknowledgments normally appear.
-.\"
-.\" 4. The names "Apache" and "Apache Software Foundation" must
-.\" not be used to endorse or promote products derived from this
-.\" software without prior written permission. For written
-.\" permission, please contact apache@xxxxxxxxxxx
-.\"
-.\" 5. Products derived from this software may not be called "Apache",
-.\" nor may "Apache" appear in their name, without prior written
-.\" permission of the Apache Software Foundation.
-.\"
-.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
-.\" WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-.\" DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
-.\" ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
-.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
-.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" This software consists of voluntary contributions made by many
-.\" individuals on behalf of the Apache Software Foundation. For more
-.\" information on the Apache Software Foundation, please see
-.\" <http://www.apache.org/>.
-.\"
+.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+.\" DO NOT EDIT! Generated from XML source.
+.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "APXS" 8 "2003-04-29" "Apache HTTP Server" "apxs"
+
.SH NAME
apxs \- APache eXtenSion tool
-.SH SYNOPSIS
-.B apxs
-.B \-g
-[
-.BI \-S " name=value
-]
-.BI \-n " modname"
-
-.B apxs
-.B \-q
-[
-.BI \-S " name=value
-]
-.IR query " ..."
-
-.B apxs
-.B \-c
-[
-.BI \-S " name=value
-]
-[
-.BI \-o " dsofile"
-]
-[
-.BI \-I " incdir"
-]
-[
-.BI \-D " name=value"
-]
-[
-.BI \-L " libdir"
-]
-[
-.BI \-l " libname"
-]
-[
-.BI \-Wc, "compiler-flags"
-]
-[
-.BI \-Wl, "linker-flags"
-]
-.IR files " ..."
-
-.B apxs
-.B \-i
-[
-.BI \-S " name=value
-]
-[
-.BI \-n " modname"
-]
-[
-.B \-a
-]
-[
-.B \-A
-]
-.IR dsofile " ..."
-
-.B apxs
-.B \-e
-[
-.BI \-S " name=value
-]
-[
-.BI \-n " modname"
-]
-[
-.B \-a
-]
-[
-.B \-A
-]
-.IR dsofile " ..."
-.PP
-.SH DESCRIPTION
-.B apxs
-is a tool for building and installing extension modules for the Apache
-HyperText Transfer Protocol (HTTP) server. This is achieved by building a
-dynamic shared object (DSO) from one or more source or object
-.I files
-which then can be loaded into
-the Apache server under runtime via the
-.B LoadModule
-directive from
-.BR mod_so.
-
-So to use this extension mechanism your platform has
-to support the DSO feature and your
-Apache
-.B httpd
-binary has to be built with the
-.B mod_so
-module.
-The
-.B apxs
-tool automatically complains if this is not the case.
-You can check this yourself by manually running the command
-
-.nf
- $ httpd -l
-.fi

-The module
-.B mod_so
-should be part of the displayed list.
-If these requirements are fulfilled you can easily extend
-your Apache server's functionality by installing your own
-modules with the DSO mechanism by the help of this
-.B apxs
-tool:
+.SH "SYNOPSIS"
+
+.PP
+\fBapxs\fR -\fBg\fR [ -\fBS\fR \fIname\fR=\fIvalue\fR ] -\fBn\fR
\fImodname\fR
+
+.PP
+\fBapxs\fR -\fBq\fR [ -\fBS\fR \fIname\fR=\fIvalue\fR ] \fIquery\fR \&.\&.\&.
+
+.PP
+\fBapxs\fR -\fBc\fR [ -\fBS\fR \fIname\fR=\fIvalue\fR ] [ -\fBo\fR
\fIdsofile\fR ] [ -\fBI\fR \fIincdir\fR ] [ -\fBD\fR \fIname\fR=\fIvalue\fR ] [
-\fBL\fR \fIlibdir\fR ] [ -\fBl\fR \fIlibname\fR ] [
-\fBWc,\fR\fIcompiler-flags\fR ] [ -\fBWl,\fR\fIlinker-flags\fR ] \fIfiles\fR
\&.\&.\&.
+
+.PP
+\fBapxs\fR -\fBi\fR [ -\fBS\fR \fIname\fR=\fIvalue\fR ] [ -\fBn\fR
\fImodname\fR ] [ -\fBa\fR ] [ -\fBA\fR ] \fIdso-file\fR \&.\&.\&.
+
+.PP
+\fBapxs\fR -\fBe\fR [ -\fBS\fR \fIname\fR=\fIvalue\fR ] [ -\fBn\fR
\fImodname\fR ] [ -\fBa\fR ] [ -\fBA\fR ] \fIdso-file\fR \&.\&.\&.
+

+.SH "SUMMARY"
+
+.PP
+apxs is a tool for building and installing extension modules for the Apache
HyperText Transfer Protocol (HTTP) server\&. This is achieved by building a
dynamic shared object (DSO) from one or more source or object \fIfiles\fR which
then can be loaded into the Apache server under runtime via the LoadModule
directive from mod_so\&.
+
+.PP
+So to use this extension mechanism your platform has to support the DSO
feature and your Apache httpd binary has to be built with the mod_so module\&.
The apxs tool automatically complains if this is not the case\&. You can check
this yourself by manually running the command
+
.nf
- $ apxs -i -a -c mod_foo.c
- gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo.c
- ld -Bshareable -o mod_foo.so mod_foo.o
- cp mod_foo.so /path/to/apache/modules/mod_foo.so
- chmod 755 /path/to/apache/modules/mod_foo.so
- [activating module `foo' in /path/to/apache/etc/httpd.conf]
- $ apachectl restart
- /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
- [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
- /path/to/apache/sbin/apachectl restart: httpd started
- $ _
-.fi

-The arguments
-.I files
-can be any C source file (.c), a object file (.o) or
-even a library archive (.a). The
-.B apxs
-tool automatically recognizes these extensions and automatically used the C
-source files for compilation while just using the object and archive files
for
-the linking phase. But when using such pre-compiled objects make sure they
are
-compiled for position independent code (PIC) to be able to use them for a
-dynamically loaded shared object.
-For instance with GCC you always just have to use
-.BR -fpic .
-For other
-C compilers consult its manual
-page or at watch for the flags
-.B apxs
-uses to compile the object files.
-
-For more details about DSO support in Apache read the documentation
-of
-.B mod_so
-or perhaps even read the
-.B src/modules/standard/mod_so.c
-source file.
-
-.PP
-.SH OPTIONS
-Common options:
-.TP 12
-.BI \-n " modname"
-This explicitly sets the module name for the
-.B \-i
-(install)
-and
-.B \-g
-(template generation) option. Use this to explicitly specify the module name.
-For option
-.B \-g
-this is required, for option
-.B \-i
-the
-.B apxs
-tool tries to determine the name from the source or (as a fallback) at least
-by guessing it from the filename.
-.PP
-Query options:
-.TP 12
-.B \-q
-Performs a query for
-.BR apxs 's
-knowledge about certain settings. The
-.I query
-parameters can be one or more of the following strings:
-.nf
- CC TARGET
- CFLAGS SBINDIR
- CFLAGS_SHLIB INCLUDEDIR
- LD_SHLIB LIBEXECDIR
- LDFLAGS_SHLIB SYSCONFDIR
- LIBS_SHLIB
+ $ httpd -l
+
.fi
-Use this for manually determining settings. For instance use
+
+.PP
+The module mod_so should be part of the displayed list\&. If these
requirements are fulfilled you can easily extend your Apache server's
functionality by installing your own modules with the DSO mechanism by the help
of this apxs tool:
+
.nf
- INC=-I`apxs -q INCLUDEDIR`
+
+ $ apxs -i -a -c mod_foo\&.c
+ gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo\&.c
+ ld -Bshareable -o mod_foo\&.so mod_foo\&.o
+ cp mod_foo\&.so /path/to/apache/modules/mod_foo\&.so
+ chmod 755 /path/to/apache/modules/mod_foo\&.so
+ [activating module `foo' in /path/to/apache/etc/httpd\&.conf]
+ $ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to
start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so\&.c(303): loaded module
foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _
+
.fi
-inside your own Makefiles if you need manual access
-to Apache's C header files.
+
+.PP
+The arguments \fIfiles\fR can be any C source file (\&.c), a object file
(\&.o) or even a library archive (\&.a)\&. The apxs tool automatically
recognizes these extensions and automatically used the C source files for
compilation while just using the object and archive files for the linking
phase\&. But when using such pre-compiled objects make sure they are compiled
for position independent code (PIC) to be able to use them for a dynamically
loaded shared object\&. For instance with GCC you always just have to use
-fpic\&. For other C compilers consult its manual page or at watch for the
flags apxs uses to compile the object files\&.
+
.PP
-Configuration options:
-.TP 12
-.BI \-S " name=value"
-This option changes the apxs settings described above.
-.PP
-Template Generation options:
-.TP 12
-.B \-g
-This generates a subdirectory
-.I name
-(see option
-.BR \-n ")"
-and there two files: A sample module source file named
-.BI mod_ name.c
-which can be used as a template for creating your own modules or
-as a quick start for playing with the APXS mechanism.
-And a corresponding
-.B Makefile
-for even easier build and installing of this module.
-.PP
-DSO compilation options:
-.TP 12
-.B \-c
-This indicates the compilation operation. It first compiles the C source
-files (.c) of
-.I files
-into corresponding object files (.o) and then builds a dynamically shared
object in
-.I dsofile
-by linking these object files plus the remaining
-object files (.o and .a) of
-.I files
-If no
-.B \-o
-option is specified
-the output file is guessed from the first filename in
-.I files
-and thus usually defaults to
-.BI mod_ name.so
-.TP 12
-.BI \-o " dsofile"
-Explicitly specifies the filename of the created dynamically shared object.
If
-not specified and the name cannot be guessed from the
-.I files
-list, the fallback name
-.B mod_unknown.so
-is used.
-.TP 12
-.BI \-D " name=value"
-This option is directly passed through to the compilation command(s).
-Use this to add your own defines to the build process.
-.TP 12
-.BI \-I " incdir"
-This option is directly passed through to the compilation command(s).
-Use this to add your own include directories to search to the build process.
-.TP 12
-.BI \-L " libdir"
-This option is directly passed through to the linker command.
-Use this to add your own library directories to search to the build process.
-.TP 12
-.BI \-l " libname"
-This option is directly passed through to the linker command.
-Use this to add your own libraries to search to the build process.
-.TP 12
-.BI \-Wc, "compiler-flags"
-This option passes
-.I compiler-flags
-as additional flags to the compiler command.
-Use this to add local compiler-specific options.
-.TP 12
-.BI \-Wl, "linker-flags"
-This option passes
-.I linker-flags
-as additional flags to the linker command.
-Use this to add local linker-specific options.
-.PP
-DSO installation and configuration options:
-.TP 12
-.B \-i
-This indicates the installation operation and installs one or more
-dynamically shared objects into the
-server's
-.I modules
-directory.
-.TP 12
-.B \-a
-This activates the module by automatically adding a corresponding
-.B LoadModule
-line to Apache's
-.B httpd.conf
-configuration file, or by enabling it if it already exists.
-.TP 12
-.B \-A
-Same as option
-.B \-a
-but the created
-.B LoadModule
-directive is prefixed with a hash sign (#), i.e. the module is
-just prepared for later activation but initially disabled.
-.TP 12
-.B \-e
-This indicates the editing operation, which can be used with the
-.B \-a
-and
-.B \-A
-options similarly to the
-.B \-i
-operation to edit Apache's
-.B httpd.conf
-configuration file without attempting to install the module.
-.PD
-.SH EXAMPLES
-Assume you have an Apache module named mod_foo.c available which should
extend
-Apache's server functionality. To accomplish this you first have to compile
-the C source into a shared object suitable for loading into the Apache server
-under runtime via the following command:
+For more details about DSO support in Apache read the documentation of
mod_so or perhaps even read the src/modules/standard/mod_so\&.c source file\&.
+

+.SH "OPTIONS"
+
+.Sh "COMMON OPTIONS"
+
+.RS
+
+.TP
+-n \fImodname\fR
+This explicitly sets the module name for the -i (install) and -g (template
generation) option\&. Use this to explicitly specify the module name\&. For
option -g this is required, for option -i the apxs tool tries to determine the
name from the source or (as a fallback) at least by guessing it from the
filename\&.
+.RE
+
+.Sh "QUERY OPTIONS"
+
+.RS
+
+.TP
+-q
+Performs a query for apxs's knowledge about certain settings\&. The
\fIquery\fR parameters can be one or more of the following strings: CC, CFLAGS,
CFLAGS_SHLIB, INCLUDEDIR, LD_SHLIB, LDFLAGS_SHLIB, LIBEXECDIR, LIBS_SHLIB,
SBINDIR, SYSCONFDIR, TARGET\&. .PP Use this for manually determining
settings\&. For instance use .nf INC=-I`apxs -q INCLUDEDIR` .fi .PP inside your
own Makefiles if you need manual access to Apache's C header files\&.
+.RE
+
+.Sh "CONFIGURATION OPTIONS"
+
+.RS
+
+.TP
+-S \fIname\fR=\fIvalue\fR
+This option changes the apxs settings described above\&.
+.RE
+
+.Sh "TEMPLATE GENERATION OPTIONS"
+
+.RS
+
+.TP
+-g
+This generates a subdirectory \fIname\fR (see option -n) and there two
files: A sample module source file named mod_\fIname\fR\&.c which can be used
as a template for creating your own modules or as a quick start for playing
with the apxs mechanism\&. And a corresponding Makefile for even easier build
and installing of this module\&.
+.RE
+
+.Sh "DSO COMPILATION OPTIONS"
+
+.RS
+
+.TP
+-c
+This indicates the compilation operation\&. It first compiles the C source
files (\&.c) of \fIfiles\fR into corresponding object files (\&.o) and then
builds a dynamically shared object in \fIdsofile\fR by linking these object
files plus the remaining object files (\&.o and \&.a) of \fIfiles\fR\&. If no
-o option is specified the output file is guessed from the first filename in
\fIfiles\fR and thus usually defaults to mod_\fIname\fR\&.so\&.
+.TP
+-o \fIdsofile\fR
+Explicitly specifies the filename of the created dynamically shared
object\&. If not specified and the name cannot be guessed from the \fIfiles\fR
list, the fallback name mod_unknown\&.so is used\&.
+.TP
+-D \fIname\fR=\fIvalue\fR
+This option is directly passed through to the compilation command(s)\&. Use
this to add your own defines to the build process\&.
+.TP
+-I \fIincdir\fR
+This option is directly passed through to the compilation command(s)\&. Use
this to add your own include directories to search to the build process\&.
+.TP
+-L \fIlibdir\fR
+This option is directly passed through to the linker command\&. Use this to
add your own library directories to search to the build process\&.
+.TP
+-l \fIlibname\fR
+This option is directly passed through to the linker command\&. Use this to
add your own libraries to search to the build process\&.
+.TP
+-Wc,\fIcompiler-flags\fR
+This option passes \fIcompiler-flags\fR as additional flags to the compiler
command\&. Use this to add local compiler-specific options\&.
+.TP
+-Wl,\fIlinker-flags\fR
+This option passes \fIlinker-flags\fR as additional flags to the linker
command\&. Use this to add local linker-specific options\&.
+.RE
+
+.Sh "DSO INSTALLATION AND CONFIGURATION OPTIONS"
+
+.RS
+
+.TP
+-i
+This indicates the installation operation and installs one or more
dynamically shared objects into the server's \fImodules\fR directory\&.
+.TP
+-a
+This activates the module by automatically adding a corresponding LoadModule
line to Apache's httpd\&.conf configuration file, or by enabling it if it
already exists\&.
+.TP
+-A
+Same as option -a but the created LoadModule directive is prefixed with a
hash sign (#), \fIi\&.e\&.\fR, the module is just prepared for later activation
but initially disabled\&.
+.TP
+-e
+This indicates the editing operation, which can be used with the -a and -A
options similarly to the -i operation to edit Apache's httpd\&.conf
configuration file without attempting to install the module\&.
+.RE
+
+.SH "EXAMPLES"
+
+.PP
+Assume you have an Apache module named mod_foo\&.c available which should
extend Apache's server functionality\&. To accomplish this you first have to
compile the C source into a shared object suitable for loading into the Apache
server under runtime via the following command:
+
.nf
- $ apxs -c mod_foo.c
- gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo.c
- ld -Bshareable -o mod_foo.so mod_foo.o
- $ _
-.fi
-
-Then you have to update the Apache configuration by making sure a
-.B LoadModule
-directive is present to load this shared object. To simplify this
-step
-.B apxs
-provides an automatic way to install the shared object in its
-"modules" directory and updating the
-.B httpd.conf
-file accordingly. This can be achieved by running:

-.nf
- $ apxs -i -a mod_foo.c
- cp mod_foo.so /path/to/apache/modules/mod_foo.so
- chmod 755 /path/to/apache/modules/mod_foo.so
- [activating module `foo' in /path/to/apache/etc/httpd.conf]
- $ _
+ $ apxs -c mod_foo\&.c
+ gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo\&.c
+ ld -Bshareable -o mod_foo\&.so mod_foo\&.o
+ $ _
+
.fi
+
+.PP
+Then you have to update the Apache configuration by making sure a LoadModule
directive is present to load this shared object\&. To simplify this step apxs
provides an automatic way to install the shared object in its "modules"
directory and updating the httpd\&.conf file accordingly\&. This can be
achieved by running:
+
+.nf

+ $ apxs -i -a mod_foo\&.c
+ cp mod_foo\&.so /path/to/apache/modules/mod_foo\&.so
+ chmod 755 /path/to/apache/modules/mod_foo\&.so
+ [activating module `foo' in /path/to/apache/etc/httpd\&.conf]
+ $ _
+
+.fi
+
+.PP
This way a line named
-
+
.nf
- LoadModule foo_module modules/mod_foo.so
-.fi
-
-is added to the configuration file if still not present.
-If you want to have this disabled per default use the
-.B \-A
-option, i.e.

-.nf
- $ apxs -i -A mod_foo.c
+ LoadModule foo_module modules/mod_foo\&.so
+
.fi
-
-For a quick test of the APXS mechanism you can create a sample Apache module
-template plus a corresponding Makefile via:
-
+
+.PP
+is added to the configuration file if still not present\&. If you want to
have this disabled per default use the -A option, \fIi\&.e\&.\fR
+
.nf
- $ apxs -g -n foo
- Creating [DIR] foo
- Creating [FILE] foo/Makefile
- Creating [FILE] foo/mod_foo.c
- $ _
-.fi
-
-Then you can immediately compile this sample module into a shared object and
-load it into the Apache server:

-.nf
- $ cd foo
- $ make all reload
- apxs -c mod_foo.c
- gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo.c
- ld -Bshareable -o mod_foo.so mod_foo.o
- apxs -i -a -n "foo" mod_foo.so
- cp mod_foo.so /path/to/apache/modules/mod_foo.so
- chmod 755 /path/to/apache/modules/mod_foo.so
- [activating module `foo' in /path/to/apache/etc/httpd.conf]
- apachectl restart
- /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
- [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
- /path/to/apache/sbin/apachectl restart: httpd started
- $ _
+ $ apxs -i -A mod_foo\&.c
+
.fi
+
+.PP
+For a quick test of the apxs mechanism you can create a sample Apache module
template plus a corresponding Makefile via:
+
+.nf

-You can even use
-.B apxs
-to compile complex modules outside the Apache source tree, like PHP3:
-
+ $ apxs -g -n foo
+ Creating [DIR] foo
+ Creating [FILE] foo/Makefile
+ Creating [FILE] foo/mod_foo\&.c
+ $ _
+
+.fi
+
+.PP
+Then you can immediately compile this sample module into a shared object and
load it into the Apache server:
+
.nf
- $ cd php3
- $ ./configure --with-shared-apache=../apache-1.3
- $ apxs -c -o libphp3.so mod_php3.c libmodphp3-so.a
- gcc -fpic -DSHARED_MODULE -I/tmp/apache/include -c mod_php3.c
- ld -Bshareable -o libphp3.so mod_php3.o libmodphp3-so.a
- $ _
+
+ $ cd foo
+ $ make all reload
+ apxs -c mod_foo\&.c
+ gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo\&.c
+ ld -Bshareable -o mod_foo\&.so mod_foo\&.o
+ apxs -i -a -n "foo" mod_foo\&.so
+ cp mod_foo\&.so /path/to/apache/modules/mod_foo\&.so
+ chmod 755 /path/to/apache/modules/mod_foo\&.so
+ [activating module `foo' in /path/to/apache/etc/httpd\&.conf]
+ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to
start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so\&.c(303): loaded module
foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _
+
.fi
+
+.PP
+You can even use apxs to compile complex modules outside the Apache source
tree, like PHP3:
+
+.nf

-because
-.B apxs
-automatically recognized C source files and object files. Only C source
files
-are compiled while remaining object files are used for the linking phase.
-
-.PD
-.SH SEE ALSO
-.BR apachectl(1),
-.BR httpd(8).
-.
+ $ cd php3
+ $ \&./configure --with-shared-apache=\&.\&./apache-1\&.3
+ $ apxs -c -o libphp3\&.so mod_php3\&.c libmodphp3-so\&.a
+ gcc -fpic -DSHARED_MODULE -I/tmp/apache/include -c mod_php3\&.c
+ ld -Bshareable -o libphp3\&.so mod_php3\&.o libmodphp3-so\&.a
+ $ _
+
+.fi
+
+.PP
+because apxs automatically recognized C source files and object files\&.
Only C source files are compiled while remaining object files are used for the
linking phase\&.
+

No revision

No revision

1.1.2.1 +2 -2 httpd-2.0/docs/manual/programs/apxs.html.en

Index: apxs.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/programs/apxs.html.en,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- apxs.html.en 29 Apr 2003 23:07:52 -0000 1.1
+++ apxs.html.en 29 Apr 2003 23:15:24 -0000 1.1.2.1
@@ -12,11 +12,11 @@
<link href="../images/favicon.ico" rel="shortcut icon" /></head>
<body id="manual-page"><div id="page-header">
<p class="menu"><a href="../mod/">Modules</a> | <a
href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a
href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
-<p class="apache">Apache HTTP Server Version 2.1</p>
+<p class="apache">Apache HTTP Server Version 2.0</p>
<img alt="" src="../images/feather.gif" /></div>
<div class="up"><a href="./"><img title="<-" alt="<-"
src="../images/left.gif" /></a></div>
<div id="path">
-<a href="http://www.apache.org/";>Apache</a> > <a
href="http://httpd.apache.org/";>HTTP Server</a> > <a
href="http://httpd.apache.org/docs-project/";>Documentation</a> > <a
href="../">Version 2.1</a> > <a href="./">Programs</a></div><div
id="page-content"><div id="preamble"><h1>apxs - APache eXtenSion tool</h1>
+<a href="http://www.apache.org/";>Apache</a> > <a
href="http://httpd.apache.org/";>HTTP Server</a> > <a
href="http://httpd.apache.org/docs-project/";>Documentation</a> > <a
href="../">Version 2.0</a> > <a href="./">Programs</a></div><div
id="page-content"><div id="preamble"><h1>apxs - APache eXtenSion tool</h1>
<p><code>apxs</code> is a tool for building and installing extension
modules for the Apache HyperText Transfer Protocol (HTTP) server. This is
achieved by building a dynamic shared object (DSO) from one or more
source

1.1.2.1 +0 -0 httpd-2.0/docs/manual/programs/apxs.xml

Index: apxs.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/programs/apxs.xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1

1.1.2.1 +0 -0 httpd-2.0/docs/manual/programs/apxs.xml.meta

Index: apxs.xml.meta
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/programs/apxs.xml.meta,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1

No revision

No revision

1.2.2.4 +0 -1 httpd-2.0/docs/manual/style/chm/hhc.xsl

Index: hhc.xsl
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/style/chm/hhc.xsl,v
retrieving revision 1.2.2.3
retrieving revision 1.2.2.4
diff -u -r1.2.2.3 -r1.2.2.4
--- hhc.xsl 29 Apr 2003 20:32:42 -0000 1.2.2.3
+++ hhc.xsl 29 Apr 2003 23:15:24 -0000 1.2.2.4
@@ -84,7 +84,6 @@

<not-exists>
<file>developer/API.xml</file>
- <file>programs/apxs.xml</file>
<file>programs/dbmmanage.xml</file>
<file>programs/htdigest.xml</file>
<file>programs/htpasswd.xml</file>

No revision

No revision

1.1.2.4 +17 -0 httpd-2.0/docs/manual/style/man/manpage.xsl

Index: manpage.xsl
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/style/man/manpage.xsl,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- manpage.xsl 29 Apr 2003 20:19:11 -0000 1.1.2.3
+++ manpage.xsl 29 Apr 2003 23:15:24 -0000 1.1.2.4
@@ -252,6 +252,23 @@


+
+
+
+<xsl:template match="section/section">
+&lf;
+<xsl:text>.Sh "</xsl:text>
+ <xsl:call-template name="filter.escape">
+ <xsl:with-param name="text"
+ select="normalize-space(translate(title, $lowercase,
$uppercase))"/>
+ </xsl:call-template>
+<xsl:text>"</xsl:text>&lf;
+<xsl:apply-templates />
+</xsl:template>
+
+
+
+

Previous by Date:	cvs commit: httpd-2.0/docs/manual/style/man manpage.xsl, nd
Next by Date:	cvs commit: apache-1.3/src CHANGES, thommay
Previous by Thread:	cvs commit: httpd-2.0/docs/manual/style/man manpage.xsl, nd
Next by Thread:	cvs commit: httpd-2.0/docs/manual/programs ab.xml ab.xml.meta ab.html, nd
Indexes:	[Date] [Thread] [Top] [All Lists]

cvs commit: httpd-2.0/docs/manual/style/man manpage.xsl: msg#00403

apache.cvs

Free Magazines

<Prev in Thread]	Current Thread	[Next in Thread>