From 84dc3c4daae48410e767ac41da148ac5c6c45446 Mon Sep 17 00:00:00 2001 From: Perl 5 Porters Date: Sat, 24 Aug 1996 23:56:18 +0000 Subject: Clean up docmentation installation errors. --- pod/perlxstut.pod | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'pod/perlxstut.pod') diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod index 592f2ee189..85a8c71f3f 100644 --- a/pod/perlxstut.pod +++ b/pod/perlxstut.pod @@ -88,7 +88,7 @@ test" is sufficient. Our first extension will be very simple. When we call the routine in the extension, it will print out a well-known message and return. -Run "h2xs -A -n Mytest". This creates a directory named Mytest, possibly under +Run C. This creates a directory named Mytest, possibly under ext/ if that directory exists in the current working directory. Several files will be created in the Mytest dir, including MANIFEST, Makefile.PL, Mytest.pm, Mytest.xs, test.pl, and Changes. @@ -271,7 +271,7 @@ contain the shared library that we will build. Once we have tested it, we can install it into its final location. Invoking the test script via "make test" did something very important. It -invoked perl with all those -I arguments so that it could find the various +invoked perl with all those C<-I> arguments so that it could find the various files that are part of the extension. It is I important that while you are still testing extensions that @@ -582,11 +582,13 @@ for equality, but rather the difference being below a certain epsilon factor, Run "make test" and all should be well. -=head 2 WHAT HAS HAPPENED HERE? +=head2 WHAT HAS HAPPENED HERE? Unlike previous examples, we've now run h2xs on a real include file. This has caused some extra goodies to appear in both the .pm and .xs files. +=over 4 + =item * In the .xs file, there's now a #include declaration with the full path to -- cgit v1.2.1