gozer 2004/09/17 21:22:49
Modified: src/docs/2.0/user/install install.pod
Log:
Clarified install doc wrt. static/dynamic builds.
Revision Changes Path
1.64 +34 -16 modperl-docs/src/docs/2.0/user/install/install.pod
Index: install.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/install/install.pod,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- install.pod 16 Sep 2004 01:15:48 -0000 1.63
+++ install.pod 18 Sep 2004 04:22:49 -0000 1.64
@@ -306,9 +306,6 @@
=head2 Configuring mod_perl
-Before you proceed make sure that Apache 2.0 has been built and
-installed. mod_perl B<cannot> be built before that.
-
To build mod_perl, you B<must> also use the same compiler that Perl
was built with. You can find that out by running C<perl -V> and
looking at the C<Compiler:> section.
@@ -322,13 +319,20 @@
where I<options> is an optional list of (key,value) pairs.
The following sections give the details about all the available
-options, but let's mention first the most important ones.
+options, but let's mention first an important one.
If you want to have mod_perl 1.0 and 2.0 installed under the same perl
tree you need to enable C<L<MP_INST_APACHE2|/MP_INST_APACHE2>>:
% perl Makefile.PL MP_INST_APACHE2=1 <other options>
+Configure Options are discussed in L<Build Options|/mod_perl_Build_Options>
+
+=head3 Dynamic mod_perl
+
+Before you proceed, make sure that Apache 2.0 has been built and
+installed. mod_perl B<cannot> be built before that.
+
It seems that most users use pre-packaged Apache installation, most of
which tend to spread the Apache files across many directories
(i.e. not using --enable-layout=Apache, which puts all the files under
@@ -357,7 +361,25 @@
% perl Makefile.PL MP_INST_APACHE2=1 MP_AP_PREFIX=$HOME/httpd/prefork
-These and other options are discussed in the following sections.
+=head3 Static mod_perl
+
+Before you proceed make sure that Apache 2.0 has been downloaded and
+extracted. mod_perl B<cannot> be build before that.
+
+To enable statically linking mod_perl into Apache, use the
+C<L<MP_USE_STATIC|/MP_USE_STATIC>> flag like this:
+
+ % perl Makefile.PL MP_USE_STATIC=1 MP_AP_BUILD=1 \
+ MP_AP_PREFIX=$HOME/src/httpd-2.x \
+ MP_AP_CONFIGURE="--with-mpm=prefork"
+
+C<L<MP_AP_PREFIX|/MP_AP_PREFIX>> B<must> point to an extrated Apache
+2.0 source tree.
+
+This will configure Apache by passing C<L<MP_AP_CONFIGURE|/MP_AP_CONFIGURE>>
+to Apache's F<./configure> script.
+
+=head2 mod_perl Build Options
=head3 Boolean Build Options
@@ -383,10 +405,6 @@
Build static mod_perl (I<mod_perl.a>). This is the default. It'll be
turned off if C<MP_USE_DSO=1> is used.
-C<MP_USE_DSO> and C<MP_USE_STATIC> are both enabled by default. So
-mod_perl is built once as I<mod_perl.a> and I<mod_perl.so>, but
-afterwards you can choose which of the two to use.
-
=head4 MP_AP_BUILD
Configure and build httpd in C<MP_AP_PREFIX>, linking mod_perl statically
@@ -491,6 +509,13 @@
I</home/httpd/httpd-2.0> as DSO, the default location would be
I</home/httpd/httpd-2.0/bin/apxs>.
+=head4 MP_AP_CONFIGURE
+
+The command-line arguments to pass to httpd's configure script.
+
+C<MP_AP_CONFIGURE> has no effect unless C<MP_AP_BUILD> is also
+specified.
+
=head4 MP_AP_PREFIX
Apache installation prefix, under which the I<include/> directory with
@@ -583,13 +608,6 @@
environment variable C<APACHE_TEST_COLOR> to 1 to enable the colored
tracing which makes it easier to tell the reported errors and
warnings, from the rest of the notifications.
-
-=head4 MP_AP_CONFIGURE
-
-The command-line arguments to pass to httpd's configure script.
-
-C<MP_AP_CONFIGURE> has no effect unless C<MP_AP_BUILD> is also
-specified.
=head2 Re-using Configure Options
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
