summaryrefslogtreecommitdiff
path: root/doc/pcre2build.3
diff options
context:
space:
mode:
authorph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069>2020-04-15 16:34:36 +0000
committerph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069>2020-04-15 16:34:36 +0000
commit6b1bd6c3d8e3b4146d303a387c85363849768701 (patch)
tree2ebc321092f042de91eb9f989e8a8f49fcb4e005 /doc/pcre2build.3
parentf06c10cc600da7eb164d85f7e143d9949d6c4b15 (diff)
downloadpcre2-6b1bd6c3d8e3b4146d303a387c85363849768701.tar.gz
File tidies for 10.35-RC1 release candidate.
git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@1244 6239d852-aaf2-0410-a92c-79f79f948069
Diffstat (limited to 'doc/pcre2build.3')
-rw-r--r--doc/pcre2build.320
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/pcre2build.3 b/doc/pcre2build.3
index a5b6718..0c469f0 100644
--- a/doc/pcre2build.3
+++ b/doc/pcre2build.3
@@ -338,23 +338,23 @@ host and therefore not compiled with the cross compiler.
If you need to create alternative tables when cross compiling, you will have to
do so "by hand". There may also be other reasons for creating tables manually.
To cause \fBpcre2_dftables\fP to be built on the local host, run a normal
-compiling command, and then run the program with the output file as its
+compiling command, and then run the program with the output file as its
argument, for example:
.sp
cc src/pcre2_dftables.c -o pcre2_dftables
- ./pcre2_dftables src/pcre2_chartables.c
+ ./pcre2_dftables src/pcre2_chartables.c
.sp
-This builds the tables in the default locale of the local host. If you want to
+This builds the tables in the default locale of the local host. If you want to
specify a locale, you must use the -L option:
.sp
LC_ALL=fr_FR ./pcre2_dftables -L src/pcre2_chartables.c
-.sp
-You can also specify -b (with or without -L). This causes the tables to be
-written in binary instead of as source code. A set of binary tables can be
-loaded into memory by an application and passed to \fBpcre2_compile()\fP in the
-same way as tables created by calling \fBpcre2_maketables()\fP. The tables are
-just a string of bytes, independent of hardware characteristics such as
-endianness. This means they can be bundled with an application that runs in
+.sp
+You can also specify -b (with or without -L). This causes the tables to be
+written in binary instead of as source code. A set of binary tables can be
+loaded into memory by an application and passed to \fBpcre2_compile()\fP in the
+same way as tables created by calling \fBpcre2_maketables()\fP. The tables are
+just a string of bytes, independent of hardware characteristics such as
+endianness. This means they can be bundled with an application that runs in
different environments, to ensure consistent behaviour.
.
.