diff options
author | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2012-11-11 20:27:03 +0000 |
---|---|---|
committer | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2012-11-11 20:27:03 +0000 |
commit | fd5db157a2356f859e77744c4ea82fbe8aa17183 (patch) | |
tree | 8211fa9eb9550cb1a93b36fe77f6b91426dae79f /doc/pcrebuild.3 | |
parent | b330e2d8210c08dfc4c99e71b477a020cb7e29fe (diff) | |
download | pcre-fd5db157a2356f859e77744c4ea82fbe8aa17183.tar.gz |
File tidies, preparing for 8.32-RC1.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@1221 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'doc/pcrebuild.3')
-rw-r--r-- | doc/pcrebuild.3 | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/pcrebuild.3 b/doc/pcrebuild.3 index 9054ead..b9ae474 100644 --- a/doc/pcrebuild.3 +++ b/doc/pcrebuild.3 @@ -14,8 +14,8 @@ options can be selected in both Unix-like and non-Unix-like environments using the GUI facility of \fBcmake-gui\fP if you are using \fBCMake\fP instead of \fBconfigure\fP to build PCRE. .P -There is a lot more information about building PCRE without using -\fBconfigure\fP (including information about using \fBCMake\fP or building "by +There is a lot more information about building PCRE without using +\fBconfigure\fP (including information about using \fBCMake\fP or building "by hand") in the file called \fINON-AUTOTOOLS-BUILD\fP, which is part of the PCRE distribution. You should consult this file as well as the \fIREADME\fP file if you are building in a non-Unix-like environment. @@ -346,18 +346,18 @@ to the \fBconfigure\fP command. This setting implies an EBCDIC environment (for example, an IBM mainframe operating system). The --enable-ebcdic option is incompatible with --enable-utf. .P -The EBCDIC character that corresponds to an ASCII LF is assumed to have the -value 0x15 by default. However, in some EBCDIC environments, 0x25 is used. In +The EBCDIC character that corresponds to an ASCII LF is assumed to have the +value 0x15 by default. However, in some EBCDIC environments, 0x25 is used. In such an environment you should use .sp --enable-ebcdic-nl25 .sp -as well as, or instead of, --enable-ebcdic. The EBCDIC character for CR has the -same value as in ASCII, namely, 0x0d. Whichever of 0x15 and 0x25 is \fInot\fP -chosen as LF is made to correspond to the Unicode NEL character (which, in +as well as, or instead of, --enable-ebcdic. The EBCDIC character for CR has the +same value as in ASCII, namely, 0x0d. Whichever of 0x15 and 0x25 is \fInot\fP +chosen as LF is made to correspond to the Unicode NEL character (which, in Unicode, is 0x85). .P -The options that select newline behaviour, such as --enable-newline-is-cr, +The options that select newline behaviour, such as --enable-newline-is-cr, and equivalent run-time options, refer to these character values in an EBCDIC environment. . @@ -447,7 +447,7 @@ code coverage report for its test suite. To enable this, you must install .sp --enable-coverage .sp -to the \fBconfigure\fP command and build PCRE in the usual way. +to the \fBconfigure\fP command and build PCRE in the usual way. .P Note that using \fBccache\fP (a caching C compiler) is incompatible with code coverage reporting. If you have configured \fBccache\fP to run automatically @@ -471,7 +471,7 @@ then "make coverage-report". This zeroes the coverage counters, but does nothing else. .sp make coverage-baseline -.sp +.sp This captures baseline coverage information. .sp make coverage-report @@ -490,9 +490,9 @@ created at compile time (*.gcno). .sp make coverage-clean .sp -This cleans all coverage data including the generated coverage report. For more -information about code coverage, see the \fBgcov\fP and \fBlcov\fP -documentation. +This cleans all coverage data including the generated coverage report. For more +information about code coverage, see the \fBgcov\fP and \fBlcov\fP +documentation. . . .SH "SEE ALSO" |