stas 02/05/14 03:22:14
Modified: src/docs/2.0/devel/core_explained core_explained.pod
Log:
MP_GENERATE_XS=1 is the default now
Revision Changes Path
1.21 +6 -6
modperl-docs/src/docs/2.0/devel/core_explained/core_explained.pod
Index: core_explained.pod
===================================================================
RCS file:
/home/cvs/modperl-docs/src/docs/2.0/devel/core_explained/core_explained.pod,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- core_explained.pod 25 Mar 2002 17:00:37 -0000 1.20
+++ core_explained.pod 14 May 2002 10:22:13 -0000 1.21
@@ -283,20 +283,20 @@
I<xs/tables/current>. For example I<xs/maps/modperl_functions.map> is
converted into I<xs/tables/current/ModPerl/FunctionTable.pm>.
-If you don't want to do a visual check on how XS code will be
-generated, just rebuild the project starting with C<perl Makefile.PL
-MP_GENERATE_XS=1>. Otherwise run:
+If you want to do a visual check on how XS code will be generated, run:
% make xs_generate
-and verify that the autogenerated XS code under the I<./Wrap>
-directory is correct.
+and verify that the autogenerated XS code under the directory
+I<./WrapXS> is correct. Otherwise build the project normally:
+
+ % perl Makefile.PL ...
=head2 XS generation process
As mentioned before XS code is generated in the I<WrapXS> directory
either during C<perl Makefile.PL> via xs_generate() if
-C<MP_GENERATE_XS=1> is used or explicitly via:
+C<MP_GENERATE_XS=1> is used (which is the default) or explicitly via:
% make xs_generate
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
