trunk/doc/pcrebuild.3

.TH PCREBUILD 3
.SH NAME
PCRE - Perl-compatible regular expressions
.SH "PCRE BUILD-TIME OPTIONS"
.rs
.sp
This document describes the optional features of PCRE that can be selected when
the library is compiled. They are all selected, or deselected, by providing
options to the \fBconfigure\fP script that is run before the \fBmake\fP
command. The complete list of options for \fBconfigure\fP (which includes the
standard ones such as the selection of the installation directory) can be
obtained by running
.sp
  ./configure --help
.sp
The following sections describe certain options whose names begin with --enable
or --disable. These settings specify changes to the defaults for the
\fBconfigure\fP command. Because of the way that \fBconfigure\fP works,
--enable and --disable always come in pairs, so the complementary option always
exists as well, but as it specifies the default, it is not described.
.
.SH "C++ SUPPORT"
.rs
.sp
By default, the \fBconfigure\fP script will search for a C++ compiler and C++
header files. If it finds them, it automatically builds the C++ wrapper library
for PCRE. You can disable this by adding
.sp
  --disable-cpp
.sp
to the \fBconfigure\fP command.
.
.SH "UTF-8 SUPPORT"
.rs
.sp
To build PCRE with support for UTF-8 character strings, add
.sp
  --enable-utf8
.sp
to the \fBconfigure\fP command. Of itself, this does not make PCRE treat
strings as UTF-8. As well as compiling PCRE with this option, you also have
have to set the PCRE_UTF8 option when you call the \fBpcre_compile()\fP
function.
.
.SH "UNICODE CHARACTER PROPERTY SUPPORT"
.rs
.sp
UTF-8 support allows PCRE to process character values greater than 255 in the
strings that it handles. On its own, however, it does not provide any
facilities for accessing the properties of such characters. If you want to be
able to use the pattern escapes \eP, \ep, and \eX, which refer to Unicode
character properties, you must add
.sp
  --enable-unicode-properties
.sp
to the \fBconfigure\fP command. This implies UTF-8 support, even if you have
not explicitly requested it.
.P
Including Unicode property support adds around 90K of tables to the PCRE
library, approximately doubling its size. Only the general category properties
such as \fILu\fP and \fINd\fP are supported. Details are given in the
.\" HREF
\fBpcrepattern\fP
.\"
documentation.
.
.SH "CODE VALUE OF NEWLINE"
.rs
.sp
By default, PCRE treats character 10 (linefeed) as the newline character. This
is the normal newline character on Unix-like systems. You can compile PCRE to
use character 13 (carriage return) instead by adding
.sp
  --enable-newline-is-cr
.sp
to the \fBconfigure\fP command. For completeness there is also a
--enable-newline-is-lf option, which explicitly specifies linefeed as the
newline character.
.
.SH "BUILDING SHARED AND STATIC LIBRARIES"
.rs
.sp
The PCRE building process uses \fBlibtool\fP to build both shared and static
Unix libraries by default. You can suppress one of these by adding one of
.sp
  --disable-shared
  --disable-static
.sp
to the \fBconfigure\fP command, as required.
.
.SH "POSIX MALLOC USAGE"
.rs
.sp
When PCRE is called through the POSIX interface (see the
.\" HREF
\fBpcreposix\fP
.\"
documentation), additional working storage is required for holding the pointers
to capturing substrings, because PCRE requires three integers per substring,
whereas the POSIX interface provides only two. If the number of expected
substrings is small, the wrapper function uses space on the stack, because this
is faster than using \fBmalloc()\fP for each call. The default threshold above
which the stack is no longer used is 10; it can be changed by adding a setting
such as
.sp
  --with-posix-malloc-threshold=20
.sp
to the \fBconfigure\fP command.
.
.SH "LIMITING PCRE RESOURCE USAGE"
.rs
.sp
Internally, PCRE has a function called \fBmatch()\fP, which it calls repeatedly
(possibly recursively) when matching a pattern with the \fBpcre_exec()\fP
function. By controlling the maximum number of times this function may be
called during a single matching operation, a limit can be placed on the
resources used by a single call to \fBpcre_exec()\fP. The limit can be changed
at run time, as described in the
.\" HREF
\fBpcreapi\fP
.\"
documentation. The default is 10 million, but this can be changed by adding a
setting such as
.sp
  --with-match-limit=500000
.sp
to the \fBconfigure\fP command. This setting has no effect on the
\fBpcre_dfa_exec()\fP matching function.
.
.SH "HANDLING VERY LARGE PATTERNS"
.rs
.sp
Within a compiled pattern, offset values are used to point from one part to
another (for example, from an opening parenthesis to an alternation
metacharacter). By default, two-byte values are used for these offsets, leading
to a maximum size for a compiled pattern of around 64K. This is sufficient to
handle all but the most gigantic patterns. Nevertheless, some people do want to
process enormous patterns, so it is possible to compile PCRE to use three-byte
or four-byte offsets by adding a setting such as
.sp
  --with-link-size=3
.sp
to the \fBconfigure\fP command. The value given must be 2, 3, or 4. Using
longer offsets slows down the operation of PCRE because it has to load
additional bytes when handling them.
.P
If you build PCRE with an increased link size, test 2 (and test 5 if you are
using UTF-8) will fail. Part of the output of these tests is a representation
of the compiled pattern, and this changes with the link size.
.
.SH "AVOIDING EXCESSIVE STACK USAGE"
.rs
.sp
When matching with the \fBpcre_exec()\fP function, PCRE implements backtracking
by making recursive calls to an internal function called \fBmatch()\fP. In
environments where the size of the stack is limited, this can severely limit
PCRE's operation. (The Unix environment does not usually suffer from this
problem.) An alternative approach that uses memory from the heap to remember
data, instead of using recursive function calls, has been implemented to work
round this problem. If you want to build a version of PCRE that works this way,
add
.sp
  --disable-stack-for-recursion
.sp
to the \fBconfigure\fP command. With this configuration, PCRE will use the
\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory
management functions. Separate functions are provided because the usage is very
predictable: the block sizes requested are always the same, and the blocks are
always freed in reverse order. A calling program might be able to implement
optimized functions that perform better than the standard \fBmalloc()\fP and
\fBfree()\fP functions. PCRE runs noticeably more slowly when built in this
way. This option affects only the \fBpcre_exec()\fP function; it is not
relevant for the the \fBpcre_dfa_exec()\fP function.
.
.SH "USING EBCDIC CODE"
.rs
.sp
PCRE assumes by default that it will run in an environment where the character
code is ASCII (or Unicode, which is a superset of ASCII). PCRE can, however, be
compiled to run in an EBCDIC environment by adding
.sp
  --enable-ebcdic
.sp
to the \fBconfigure\fP command.
.P
.in 0
Last updated: 15 August 2005
.br
Copyright (c) 1997-2005 University of Cambridge.
1	nigel	79	.TH PCREBUILD 3
2	nigel	63	.SH NAME
3			PCRE - Perl-compatible regular expressions
4	nigel	75	.SH "PCRE BUILD-TIME OPTIONS"
5	nigel	63	.rs
6			.sp
7			This document describes the optional features of PCRE that can be selected when
8			the library is compiled. They are all selected, or deselected, by providing
9	nigel	75	options to the \fBconfigure\fP script that is run before the \fBmake\fP
10			command. The complete list of options for \fBconfigure\fP (which includes the
11	nigel	63	standard ones such as the selection of the installation directory) can be
12			obtained by running
13	nigel	75	.sp
14	nigel	63	./configure --help
15	nigel	75	.sp
16	nigel	63	The following sections describe certain options whose names begin with --enable
17			or --disable. These settings specify changes to the defaults for the
18	nigel	75	\fBconfigure\fP command. Because of the way that \fBconfigure\fP works,
19	nigel	63	--enable and --disable always come in pairs, so the complementary option always
20			exists as well, but as it specifies the default, it is not described.
21	nigel	75	.
22	nigel	83	.SH "C++ SUPPORT"
23			.rs
24			.sp
25			By default, the \fBconfigure\fP script will search for a C++ compiler and C++
26			header files. If it finds them, it automatically builds the C++ wrapper library
27			for PCRE. You can disable this by adding
28			.sp
29			--disable-cpp
30			.sp
31			to the \fBconfigure\fP command.
32			.
33	nigel	75	.SH "UTF-8 SUPPORT"
34	nigel	63	.rs
35			.sp
36			To build PCRE with support for UTF-8 character strings, add
37	nigel	75	.sp
38	nigel	63	--enable-utf8
39	nigel	75	.sp
40			to the \fBconfigure\fP command. Of itself, this does not make PCRE treat
41	nigel	63	strings as UTF-8. As well as compiling PCRE with this option, you also have
42	nigel	75	have to set the PCRE_UTF8 option when you call the \fBpcre_compile()\fP
43	nigel	63	function.
44	nigel	75	.
45			.SH "UNICODE CHARACTER PROPERTY SUPPORT"
46	nigel	63	.rs
47			.sp
48	nigel	75	UTF-8 support allows PCRE to process character values greater than 255 in the
49			strings that it handles. On its own, however, it does not provide any
50			facilities for accessing the properties of such characters. If you want to be
51			able to use the pattern escapes \eP, \ep, and \eX, which refer to Unicode
52			character properties, you must add
53			.sp
54			--enable-unicode-properties
55			.sp
56			to the \fBconfigure\fP command. This implies UTF-8 support, even if you have
57			not explicitly requested it.
58			.P
59			Including Unicode property support adds around 90K of tables to the PCRE
60			library, approximately doubling its size. Only the general category properties
61			such as \fILu\fP and \fINd\fP are supported. Details are given in the
62			.\" HREF
63			\fBpcrepattern\fP
64			.\"
65			documentation.
66			.
67			.SH "CODE VALUE OF NEWLINE"
68			.rs
69			.sp
70	nigel	63	By default, PCRE treats character 10 (linefeed) as the newline character. This
71			is the normal newline character on Unix-like systems. You can compile PCRE to
72			use character 13 (carriage return) instead by adding
73	nigel	75	.sp
74	nigel	63	--enable-newline-is-cr
75	nigel	75	.sp
76			to the \fBconfigure\fP command. For completeness there is also a
77	nigel	63	--enable-newline-is-lf option, which explicitly specifies linefeed as the
78			newline character.
79	nigel	75	.
80			.SH "BUILDING SHARED AND STATIC LIBRARIES"
81	nigel	63	.rs
82			.sp
83	nigel	75	The PCRE building process uses \fBlibtool\fP to build both shared and static
84	nigel	63	Unix libraries by default. You can suppress one of these by adding one of
85	nigel	75	.sp
86	nigel	63	--disable-shared
87			--disable-static
88	nigel	75	.sp
89			to the \fBconfigure\fP command, as required.
90			.
91			.SH "POSIX MALLOC USAGE"
92	nigel	63	.rs
93			.sp
94	nigel	75	When PCRE is called through the POSIX interface (see the
95			.\" HREF
96			\fBpcreposix\fP
97			.\"
98	nigel	63	documentation), additional working storage is required for holding the pointers
99	nigel	75	to capturing substrings, because PCRE requires three integers per substring,
100	nigel	63	whereas the POSIX interface provides only two. If the number of expected
101			substrings is small, the wrapper function uses space on the stack, because this
102	nigel	75	is faster than using \fBmalloc()\fP for each call. The default threshold above
103	nigel	63	which the stack is no longer used is 10; it can be changed by adding a setting
104			such as
105	nigel	75	.sp
106	nigel	63	--with-posix-malloc-threshold=20
107	nigel	75	.sp
108			to the \fBconfigure\fP command.
109			.
110			.SH "LIMITING PCRE RESOURCE USAGE"
111	nigel	63	.rs
112			.sp
113	nigel	75	Internally, PCRE has a function called \fBmatch()\fP, which it calls repeatedly
114	nigel	77	(possibly recursively) when matching a pattern with the \fBpcre_exec()\fP
115			function. By controlling the maximum number of times this function may be
116			called during a single matching operation, a limit can be placed on the
117			resources used by a single call to \fBpcre_exec()\fP. The limit can be changed
118			at run time, as described in the
119	nigel	75	.\" HREF
120			\fBpcreapi\fP
121			.\"
122			documentation. The default is 10 million, but this can be changed by adding a
123			setting such as
124			.sp
125	nigel	63	--with-match-limit=500000
126	nigel	75	.sp
127	nigel	77	to the \fBconfigure\fP command. This setting has no effect on the
128			\fBpcre_dfa_exec()\fP matching function.
129	nigel	75	.
130			.SH "HANDLING VERY LARGE PATTERNS"
131	nigel	63	.rs
132			.sp
133			Within a compiled pattern, offset values are used to point from one part to
134			another (for example, from an opening parenthesis to an alternation
135	nigel	75	metacharacter). By default, two-byte values are used for these offsets, leading
136	nigel	63	to a maximum size for a compiled pattern of around 64K. This is sufficient to
137			handle all but the most gigantic patterns. Nevertheless, some people do want to
138			process enormous patterns, so it is possible to compile PCRE to use three-byte
139			or four-byte offsets by adding a setting such as
140	nigel	75	.sp
141	nigel	63	--with-link-size=3
142	nigel	75	.sp
143			to the \fBconfigure\fP command. The value given must be 2, 3, or 4. Using
144	nigel	63	longer offsets slows down the operation of PCRE because it has to load
145			additional bytes when handling them.
146	nigel	75	.P
147	nigel	63	If you build PCRE with an increased link size, test 2 (and test 5 if you are
148			using UTF-8) will fail. Part of the output of these tests is a representation
149			of the compiled pattern, and this changes with the link size.
150	nigel	75	.
151			.SH "AVOIDING EXCESSIVE STACK USAGE"
152	nigel	73	.rs
153			.sp
154	nigel	77	When matching with the \fBpcre_exec()\fP function, PCRE implements backtracking
155			by making recursive calls to an internal function called \fBmatch()\fP. In
156			environments where the size of the stack is limited, this can severely limit
157			PCRE's operation. (The Unix environment does not usually suffer from this
158			problem.) An alternative approach that uses memory from the heap to remember
159			data, instead of using recursive function calls, has been implemented to work
160			round this problem. If you want to build a version of PCRE that works this way,
161			add
162	nigel	75	.sp
163	nigel	73	--disable-stack-for-recursion
164	nigel	75	.sp
165			to the \fBconfigure\fP command. With this configuration, PCRE will use the
166			\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory
167	nigel	73	management functions. Separate functions are provided because the usage is very
168			predictable: the block sizes requested are always the same, and the blocks are
169			always freed in reverse order. A calling program might be able to implement
170	nigel	75	optimized functions that perform better than the standard \fBmalloc()\fP and
171			\fBfree()\fP functions. PCRE runs noticeably more slowly when built in this
172	nigel	77	way. This option affects only the \fBpcre_exec()\fP function; it is not
173			relevant for the the \fBpcre_dfa_exec()\fP function.
174	nigel	75	.
175			.SH "USING EBCDIC CODE"
176	nigel	73	.rs
177			.sp
178			PCRE assumes by default that it will run in an environment where the character
179	nigel	75	code is ASCII (or Unicode, which is a superset of ASCII). PCRE can, however, be
180	nigel	73	compiled to run in an EBCDIC environment by adding
181	nigel	75	.sp
182	nigel	73	--enable-ebcdic
183	nigel	75	.sp
184			to the \fBconfigure\fP command.
185			.P
186	nigel	63	.in 0
187	nigel	83	Last updated: 15 August 2005
188	nigel	63	.br
189	nigel	77	Copyright (c) 1997-2005 University of Cambridge.