/[pcre]/code/trunk/doc/pcrebuild.3
ViewVC logotype

Diff of /code/trunk/doc/pcrebuild.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 195 by ph10, Mon Jul 30 13:23:28 2007 UTC revision 456 by ph10, Fri Oct 2 08:53:31 2009 UTC
# Line 1  Line 1 
1  .TH PCREBUILD 3  .TH PCREBUILD 3
2  .SH NAME  .SH NAME
3  PCRE - Perl-compatible regular expressions  PCRE - Perl-compatible regular expressions
4    .
5    .
6  .SH "PCRE BUILD-TIME OPTIONS"  .SH "PCRE BUILD-TIME OPTIONS"
7  .rs  .rs
8  .sp  .sp
9  This document describes the optional features of PCRE that can be selected when  This document describes the optional features of PCRE that can be selected when
10  the library is compiled. They are all selected, or deselected, by providing  the library is compiled. It assumes use of the \fBconfigure\fP script, where
11  options to the \fBconfigure\fP script that is run before the \fBmake\fP  the optional features are selected or deselected by providing options to
12  command. The complete list of options for \fBconfigure\fP (which includes the  \fBconfigure\fP before running the \fBmake\fP command. However, the same
13  standard ones such as the selection of the installation directory) can be  options can be selected in both Unix-like and non-Unix-like environments using
14  obtained by running  the GUI facility of \fBcmake-gui\fP if you are using \fBCMake\fP instead of
15    \fBconfigure\fP to build PCRE.
16    .P
17    There is a lot more information about building PCRE in non-Unix-like
18    environments in the file called \fINON_UNIX_USE\fP, which is part of the PCRE
19    distribution. You should consult this file as well as the \fIREADME\fP file if
20    you are building in a non-Unix-like environment.
21    .P
22    The complete list of options for \fBconfigure\fP (which includes the standard
23    ones such as the selection of the installation directory) can be obtained by
24    running
25  .sp  .sp
26    ./configure --help    ./configure --help
27  .sp  .sp
# Line 19  The following sections include descripti Line 31  The following sections include descripti
31  --enable and --disable always come in pairs, so the complementary option always  --enable and --disable always come in pairs, so the complementary option always
32  exists as well, but as it specifies the default, it is not described.  exists as well, but as it specifies the default, it is not described.
33  .  .
34    .
35  .SH "C++ SUPPORT"  .SH "C++ SUPPORT"
36  .rs  .rs
37  .sp  .sp
# Line 30  for PCRE. You can disable this by adding Line 43  for PCRE. You can disable this by adding
43  .sp  .sp
44  to the \fBconfigure\fP command.  to the \fBconfigure\fP command.
45  .  .
46    .
47  .SH "UTF-8 SUPPORT"  .SH "UTF-8 SUPPORT"
48  .rs  .rs
49  .sp  .sp
50  To build PCRE with support for UTF-8 character strings, add  To build PCRE with support for UTF-8 Unicode character strings, add
51  .sp  .sp
52    --enable-utf8    --enable-utf8
53  .sp  .sp
54  to the \fBconfigure\fP command. Of itself, this does not make PCRE treat  to the \fBconfigure\fP command. Of itself, this does not make PCRE treat
55  strings as UTF-8. As well as compiling PCRE with this option, you also have  strings as UTF-8. As well as compiling PCRE with this option, you also have
56  have to set the PCRE_UTF8 option when you call the \fBpcre_compile()\fP  have to set the PCRE_UTF8 option when you call the \fBpcre_compile()\fP
57  function.  or \fBpcre_compile2()\fP functions.
58    .P
59    If you set --enable-utf8 when compiling in an EBCDIC environment, PCRE expects
60    its input to be either ASCII or UTF-8 (depending on the runtime option). It is
61    not possible to support both EBCDIC and UTF-8 codes in the same version of the
62    library. Consequently, --enable-utf8 and --enable-ebcdic are mutually
63    exclusive.
64    .
65  .  .
66  .SH "UNICODE CHARACTER PROPERTY SUPPORT"  .SH "UNICODE CHARACTER PROPERTY SUPPORT"
67  .rs  .rs
# Line 64  supported. Details are given in the Line 85  supported. Details are given in the
85  .\"  .\"
86  documentation.  documentation.
87  .  .
88    .
89  .SH "CODE VALUE OF NEWLINE"  .SH "CODE VALUE OF NEWLINE"
90  .rs  .rs
91  .sp  .sp
92  By default, PCRE interprets character 10 (linefeed, LF) as indicating the end  By default, PCRE interprets the linefeed (LF) character as indicating the end
93  of a line. This is the normal newline character on Unix-like systems. You can  of a line. This is the normal newline character on Unix-like systems. You can
94  compile PCRE to use character 13 (carriage return, CR) instead, by adding  compile PCRE to use carriage return (CR) instead, by adding
95  .sp  .sp
96    --enable-newline-is-cr    --enable-newline-is-cr
97  .sp  .sp
# Line 96  Whatever line ending convention is selec Line 118  Whatever line ending convention is selec
118  overridden when the library functions are called. At build time it is  overridden when the library functions are called. At build time it is
119  conventional to use the standard for your operating system.  conventional to use the standard for your operating system.
120  .  .
121    .
122    .SH "WHAT \eR MATCHES"
123    .rs
124    .sp
125    By default, the sequence \eR in a pattern matches any Unicode newline sequence,
126    whatever has been selected as the line ending sequence. If you specify
127    .sp
128      --enable-bsr-anycrlf
129    .sp
130    the default is changed so that \eR matches only CR, LF, or CRLF. Whatever is
131    selected when PCRE is built can be overridden when the library functions are
132    called.
133    .
134    .
135  .SH "BUILDING SHARED AND STATIC LIBRARIES"  .SH "BUILDING SHARED AND STATIC LIBRARIES"
136  .rs  .rs
137  .sp  .sp
# Line 107  Unix libraries by default. You can suppr Line 143  Unix libraries by default. You can suppr
143  .sp  .sp
144  to the \fBconfigure\fP command, as required.  to the \fBconfigure\fP command, as required.
145  .  .
146    .
147  .SH "POSIX MALLOC USAGE"  .SH "POSIX MALLOC USAGE"
148  .rs  .rs
149  .sp  .sp
# Line 126  such as Line 163  such as
163  .sp  .sp
164  to the \fBconfigure\fP command.  to the \fBconfigure\fP command.
165  .  .
166    .
167  .SH "HANDLING VERY LARGE PATTERNS"  .SH "HANDLING VERY LARGE PATTERNS"
168  .rs  .rs
169  .sp  .sp
# Line 134  another (for example, from an opening pa Line 172  another (for example, from an opening pa
172  metacharacter). By default, two-byte values are used for these offsets, leading  metacharacter). By default, two-byte values are used for these offsets, leading
173  to a maximum size for a compiled pattern of around 64K. This is sufficient to  to a maximum size for a compiled pattern of around 64K. This is sufficient to
174  handle all but the most gigantic patterns. Nevertheless, some people do want to  handle all but the most gigantic patterns. Nevertheless, some people do want to
175  process enormous patterns, so it is possible to compile PCRE to use three-byte  process truyl enormous patterns, so it is possible to compile PCRE to use
176  or four-byte offsets by adding a setting such as  three-byte or four-byte offsets by adding a setting such as
177  .sp  .sp
178    --with-link-size=3    --with-link-size=3
179  .sp  .sp
# Line 143  to the \fBconfigure\fP command. The valu Line 181  to the \fBconfigure\fP command. The valu
181  longer offsets slows down the operation of PCRE because it has to load  longer offsets slows down the operation of PCRE because it has to load
182  additional bytes when handling them.  additional bytes when handling them.
183  .  .
184    .
185  .SH "AVOIDING EXCESSIVE STACK USAGE"  .SH "AVOIDING EXCESSIVE STACK USAGE"
186  .rs  .rs
187  .sp  .sp
# Line 166  to the \fBconfigure\fP command. With thi Line 205  to the \fBconfigure\fP command. With thi
205  \fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory  \fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory
206  management functions. By default these point to \fBmalloc()\fP and  management functions. By default these point to \fBmalloc()\fP and
207  \fBfree()\fP, but you can replace the pointers so that your own functions are  \fBfree()\fP, but you can replace the pointers so that your own functions are
208  used.  used instead.
209  .P  .P
210  Separate functions are provided rather than using \fBpcre_malloc\fP and  Separate functions are provided rather than using \fBpcre_malloc\fP and
211  \fBpcre_free\fP because the usage is very predictable: the block sizes  \fBpcre_free\fP because the usage is very predictable: the block sizes
# Line 174  requested are always the same, and the b Line 213  requested are always the same, and the b
213  order. A calling program might be able to implement optimized functions that  order. A calling program might be able to implement optimized functions that
214  perform better than \fBmalloc()\fP and \fBfree()\fP. PCRE runs noticeably more  perform better than \fBmalloc()\fP and \fBfree()\fP. PCRE runs noticeably more
215  slowly when built in this way. This option affects only the \fBpcre_exec()\fP  slowly when built in this way. This option affects only the \fBpcre_exec()\fP
216  function; it is not relevant for the the \fBpcre_dfa_exec()\fP function.  function; it is not relevant for \fBpcre_dfa_exec()\fP.
217    .
218  .  .
219  .SH "LIMITING PCRE RESOURCE USAGE"  .SH "LIMITING PCRE RESOURCE USAGE"
220  .rs  .rs
# Line 207  constraints. However, you can set a lowe Line 247  constraints. However, you can set a lowe
247  .sp  .sp
248  to the \fBconfigure\fP command. This value can also be overridden at run time.  to the \fBconfigure\fP command. This value can also be overridden at run time.
249  .  .
250    .
251  .SH "CREATING CHARACTER TABLES AT BUILD TIME"  .SH "CREATING CHARACTER TABLES AT BUILD TIME"
252  .rs  .rs
253  .sp  .sp
# Line 225  compiling, because \fBdftables\fP is run Line 266  compiling, because \fBdftables\fP is run
266  create alternative tables when cross compiling, you will have to do so "by  create alternative tables when cross compiling, you will have to do so "by
267  hand".)  hand".)
268  .  .
269    .
270  .SH "USING EBCDIC CODE"  .SH "USING EBCDIC CODE"
271  .rs  .rs
272  .sp  .sp
# Line 236  EBCDIC environment by adding Line 278  EBCDIC environment by adding
278    --enable-ebcdic    --enable-ebcdic
279  .sp  .sp
280  to the \fBconfigure\fP command. This setting implies  to the \fBconfigure\fP command. This setting implies
281  --enable-rebuild-chartables. You should only use it if you know that you are in  --enable-rebuild-chartables. You should only use it if you know that you are in
282  an EBCDIC environment (for example, an IBM mainframe operating system).  an EBCDIC environment (for example, an IBM mainframe operating system). The
283    --enable-ebcdic option is incompatible with --enable-utf8.
284    .
285    .
286    .SH "PCREGREP OPTIONS FOR COMPRESSED FILE SUPPORT"
287    .rs
288    .sp
289    By default, \fBpcregrep\fP reads all files as plain text. You can build it so
290    that it recognizes files whose names end in \fB.gz\fP or \fB.bz2\fP, and reads
291    them with \fBlibz\fP or \fBlibbz2\fP, respectively, by adding one or both of
292    .sp
293      --enable-pcregrep-libz
294      --enable-pcregrep-libbz2
295    .sp
296    to the \fBconfigure\fP command. These options naturally require that the
297    relevant libraries are installed on your system. Configuration will fail if
298    they are not.
299    .
300    .
301    .SH "PCRETEST OPTION FOR LIBREADLINE SUPPORT"
302    .rs
303    .sp
304    If you add
305    .sp
306      --enable-pcretest-libreadline
307    .sp
308    to the \fBconfigure\fP command, \fBpcretest\fP is linked with the
309    \fBlibreadline\fP library, and when its input is from a terminal, it reads it
310    using the \fBreadline()\fP function. This provides line-editing and history
311    facilities. Note that \fBlibreadline\fP is GPL-licensed, so if you distribute a
312    binary of \fBpcretest\fP linked in this way, there may be licensing issues.
313    .P
314    Setting this option causes the \fB-lreadline\fP option to be added to the
315    \fBpcretest\fP build. In many operating environments with a sytem-installed
316    \fBlibreadline\fP this is sufficient. However, in some environments (e.g.
317    if an unmodified distribution version of readline is in use), some extra
318    configuration may be necessary. The INSTALL file for \fBlibreadline\fP says
319    this:
320    .sp
321      "Readline uses the termcap functions, but does not link with the
322      termcap or curses library itself, allowing applications which link
323      with readline the to choose an appropriate library."
324    .sp
325    If your environment has not been set up so that an appropriate library is
326    automatically included, you may need to add something like
327    .sp
328      LIBS="-ncurses"
329    .sp
330    immediately before the \fBconfigure\fP command.
331  .  .
332  .  .
333  .SH "SEE ALSO"  .SH "SEE ALSO"
# Line 260  Cambridge CB2 3QH, England. Line 350  Cambridge CB2 3QH, England.
350  .rs  .rs
351  .sp  .sp
352  .nf  .nf
353  Last updated: 30 July 2007  Last updated: 29 September 2009
354  Copyright (c) 1997-2007 University of Cambridge.  Copyright (c) 1997-2009 University of Cambridge.
355  .fi  .fi

Legend:
Removed from v.195  
changed lines
  Added in v.456

  ViewVC Help
Powered by ViewVC 1.1.5