/[pcre]/code/trunk/README
ViewVC logotype

Diff of /code/trunk/README

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

revision 99 by ph10, Tue Mar 6 12:27:42 2007 UTC revision 672 by ph10, Tue Aug 23 16:45:55 2011 UTC
# Line 1  Line 1 
1  README file for PCRE (Perl-compatible regular expression library)  README file for PCRE (Perl-compatible regular expression library)
2  -----------------------------------------------------------------  -----------------------------------------------------------------
3    
4  The latest release of PCRE is always available from  The latest release of PCRE is always available in three alternative formats
5    from:
6    
7    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.gz
8      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.tar.bz2
9      ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-xxx.zip
10    
11    There is a mailing list for discussion about the development of PCRE at
12    
13      pcre-dev@exim.org
14    
15  Please read the NEWS file if you are upgrading from a previous release.  Please read the NEWS file if you are upgrading from a previous release.
16    The contents of this README file are:
17    
18      The PCRE APIs
19      Documentation for PCRE
20      Contributions by users of PCRE
21      Building PCRE on non-Unix systems
22      Building PCRE on Unix-like systems
23      Retrieving configuration information on Unix-like systems
24      Shared libraries on Unix-like systems
25      Cross-compiling on Unix-like systems
26      Using HP's ANSI C++ compiler (aCC)
27      Using PCRE from MySQL
28      Making new tarballs
29      Testing PCRE
30      Character tables
31      File manifest
32    
33    
34  The PCRE APIs  The PCRE APIs
35  -------------  -------------
36    
37  PCRE is written in C, and it has its own API. The distribution now includes a  PCRE is written in C, and it has its own API. The distribution also includes a
38  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page  set of C++ wrapper functions (see the pcrecpp man page for details), courtesy
39  for details).  of Google Inc.
40    
41  Also included are a set of C wrapper functions that are based on the POSIX  In addition, there is a set of C wrapper functions that are based on the POSIX
42  API. These end up in the library called libpcreposix. Note that this just  regular expression API (see the pcreposix man page). These end up in the
43  provides a POSIX calling interface to PCRE: the regular expressions themselves  library called libpcreposix. Note that this just provides a POSIX calling
44  still follow Perl syntax and semantics. The header file for the POSIX-style  interface to PCRE; the regular expressions themselves still follow Perl syntax
45  functions is called pcreposix.h. The official POSIX name is regex.h, but I  and semantics. The POSIX API is restricted, and does not give full access to
46  didn't want to risk possible problems with existing files of that name by  all of PCRE's facilities.
47  distributing it that way. To use it with an existing program that uses the  
48  POSIX API, it will have to be renamed or pointed at by a link.  The header file for the POSIX-style functions is called pcreposix.h. The
49    official POSIX name is regex.h, but I did not want to risk possible problems
50    with existing files of that name by distributing it that way. To use PCRE with
51    an existing program that uses the POSIX API, pcreposix.h will have to be
52    renamed or pointed at by a link.
53    
54  If you are using the POSIX interface to PCRE and there is already a POSIX regex  If you are using the POSIX interface to PCRE and there is already a POSIX regex
55  library installed on your system, you must take care when linking programs to  library installed on your system, as well as worrying about the regex.h header
56    file (as mentioned above), you must also take care when linking programs to
57  ensure that they link with PCRE's libpcreposix library. Otherwise they may pick  ensure that they link with PCRE's libpcreposix library. Otherwise they may pick
58  up the "real" POSIX functions of the same name.  up the POSIX functions of the same name from the other library.
59    
60    One way of avoiding this confusion is to compile PCRE with the addition of
61    -Dregcomp=PCREregcomp (and similarly for the other POSIX functions) to the
62    compiler flags (CFLAGS if you are using "configure" -- see below). This has the
63    effect of renaming the functions so that the names no longer clash. Of course,
64    you have to do the same thing for your applications, or write them using the
65    new names.
66    
67    
68  Documentation for PCRE  Documentation for PCRE
69  ----------------------  ----------------------
70    
71  If you install PCRE in the normal way, you will end up with an installed set of  If you install PCRE in the normal way on a Unix-like system, you will end up
72  man pages whose names all start with "pcre". The one that is just called "pcre"  with a set of man pages whose names all start with "pcre". The one that is just
73  lists all the others. In addition to these man pages, the PCRE documentation is  called "pcre" lists all the others. In addition to these man pages, the PCRE
74  supplied in two other forms; however, as there is no standard place to install  documentation is supplied in two other forms:
75  them, they are left in the doc directory of the unpacked source distribution.  
76  These forms are:    1. There are files called doc/pcre.txt, doc/pcregrep.txt, and
77         doc/pcretest.txt in the source distribution. The first of these is a
78    1. Files called doc/pcre.txt, doc/pcregrep.txt, and doc/pcretest.txt. The       concatenation of the text forms of all the section 3 man pages except
79       first of these is a concatenation of the text forms of all the section 3       those that summarize individual functions. The other two are the text
80       man pages except those that summarize individual functions. The other two       forms of the section 1 man pages for the pcregrep and pcretest commands.
81       are the text forms of the section 1 man pages for the pcregrep and       These text forms are provided for ease of scanning with text editors or
82       pcretest commands. Text forms are provided for ease of scanning with text       similar tools. They are installed in <prefix>/share/doc/pcre, where
83       editors or similar tools.       <prefix> is the installation prefix (defaulting to /usr/local).
84    
85    2. A subdirectory called doc/html contains all the documentation in HTML    2. A set of files containing all the documentation in HTML form, hyperlinked
86       form, hyperlinked in various ways, and rooted in a file called       in various ways, and rooted in a file called index.html, is distributed in
87       doc/index.html.       doc/html and installed in <prefix>/share/doc/pcre/html.
88    
89    Users of PCRE have contributed files containing the documentation for various
90    releases in CHM format. These can be found in the Contrib directory of the FTP
91    site (see next section).
92    
93    
94  Contributions by users of PCRE  Contributions by users of PCRE
# Line 59  You can find contributions from PCRE use Line 98  You can find contributions from PCRE use
98    
99    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
100    
101  where there is also a README file giving brief descriptions of what they are.  There is a README file giving brief descriptions of what they are. Some are
102  Several of them provide support for compiling PCRE on various flavours of  complete in themselves; others are pointers to URLs containing relevant files.
103  Windows systems (I myself do not use Windows). Some are complete in themselves;  Some of this material is likely to be well out-of-date. Several of the earlier
104  others are pointers to URLs containing relevant files.  contributions provided support for compiling PCRE on various flavours of
105    Windows (I myself do not use Windows). Nowadays there is more Windows support
106    in the standard distribution, so these contibutions have been archived.
107    
108    
109    Building PCRE on non-Unix systems
110    ---------------------------------
111    
112  Building PCRE on a Unix-like system  For a non-Unix system, please read the comments in the file NON-UNIX-USE,
113  -----------------------------------  though if your system supports the use of "configure" and "make" you may be
114    able to build PCRE in the same way as for Unix-like systems. PCRE can also be
115    configured in many platform environments using the GUI facility provided by
116    CMake's cmake-gui command. This creates Makefiles, solution files, etc.
117    
118    PCRE has been compiled on many different operating systems. It should be
119    straightforward to build PCRE on any system that has a Standard C compiler and
120    library, because it uses only Standard C functions.
121    
122    
123    Building PCRE on Unix-like systems
124    ----------------------------------
125    
126  If you are using HP's ANSI C++ compiler (aCC), please see the special note  If you are using HP's ANSI C++ compiler (aCC), please see the special note
127  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
128    
129    The following instructions assume the use of the widely used "configure, make,
130    make install" process. There is also support for CMake in the PCRE
131    distribution; there are some comments about using CMake in the NON-UNIX-USE
132    file, though it can also be used in Unix-like systems.
133    
134  To build PCRE on a Unix-like system, first run the "configure" command from the  To build PCRE on a Unix-like system, first run the "configure" command from the
135  PCRE distribution directory, with your current directory set to the directory  PCRE distribution directory, with your current directory set to the directory
136  where you want the files to be created. This command is a standard GNU  where you want the files to be created. This command is a standard GNU
137  "autoconf" configuration script, for which generic instructions are supplied in  "autoconf" configuration script, for which generic instructions are supplied in
138  INSTALL.  the file INSTALL.
139    
140  Most commonly, people build PCRE within its own distribution directory, and in  Most commonly, people build PCRE within its own distribution directory, and in
141  this case, on many systems, just running "./configure" is sufficient, but the  this case, on many systems, just running "./configure" is sufficient. However,
142  usual methods of changing standard defaults are available. For example:  the usual methods of changing standard defaults are available. For example:
143    
144  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
145    
# Line 99  possible to build it as a C++ library, t Line 159  possible to build it as a C++ library, t
159  does not have any features to support this.  does not have any features to support this.
160    
161  There are some optional features that can be included or omitted from the PCRE  There are some optional features that can be included or omitted from the PCRE
162  library. You can read more about them in the pcrebuild man page.  library. They are also documented in the pcrebuild man page.
163    
164    . By default, both shared and static libraries are built. You can change this
165      by adding one of these options to the "configure" command:
166    
167      --disable-shared
168      --disable-static
169    
170      (See also "Shared libraries on Unix-like systems" below.)
171    
172  . If you want to suppress the building of the C++ wrapper library, you can add  . If you want to suppress the building of the C++ wrapper library, you can add
173    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,
174    will try to find a C++ compiler and C++ header files, and if it succeeds, it    it will try to find a C++ compiler and C++ header files, and if it succeeds,
175    will try to build the C++ wrapper.    it will try to build the C++ wrapper.
176    
177  . If you want to make use of the support for UTF-8 character strings in PCRE,  . If you want to include support for just-in-time compiling, which can give
178    you must add --enable-utf8 to the "configure" command. Without it, the code    large performance improvements on certain platforms, add --enable-jit to the
179    for handling UTF-8 is not included in the library. (Even when included, it    "configure" command.
180    still has to be enabled by an option at run time.)  
181    . If you want to make use of the support for UTF-8 Unicode character strings in
182      PCRE, you must add --enable-utf8 to the "configure" command. Without it, the
183      code for handling UTF-8 is not included in the library. Even when included,
184      it still has to be enabled by an option at run time. When PCRE is compiled
185      with this option, its input can only either be ASCII or UTF-8, even when
186      running on EBCDIC platforms. It is not possible to use both --enable-utf8 and
187      --enable-ebcdic at the same time.
188    
189  . If, in addition to support for UTF-8 character strings, you want to include  . If, in addition to support for UTF-8 character strings, you want to include
190    support for the \P, \p, and \X sequences that recognize Unicode character    support for the \P, \p, and \X sequences that recognize Unicode character
# Line 119  library. You can read more about them in Line 194  library. You can read more about them in
194    supported.    supported.
195    
196  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any
197    of the Unicode newline sequences as indicating the end of a line. Whatever    of the preceding, or any of the Unicode newline sequences as indicating the
198    you specify at build time is the default; the caller of PCRE can change the    end of a line. Whatever you specify at build time is the default; the caller
199    selection at run time. The default newline indicator is a single LF character    of PCRE can change the selection at run time. The default newline indicator
200    (the Unix standard). You can specify the default newline indicator by adding    is a single LF character (the Unix standard). You can specify the default
201    --newline-is-cr or --newline-is-lf or --newline-is-crlf or --newline-is-any    newline indicator by adding --enable-newline-is-cr or --enable-newline-is-lf
202    to the "configure" command, respectively.    or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
203      --enable-newline-is-any to the "configure" command, respectively.
204    If you specify --newline-is-cr or --newline-is-crlf, some of the standard  
205    tests will fail, because the lines in the test files end with LF. Even if    If you specify --enable-newline-is-cr or --enable-newline-is-crlf, some of
206    the files are edited to change the line endings, there are likely to be some    the standard tests will fail, because the lines in the test files end with
207    failures. With --newline-is-any, many tests should succeed, but there may be    LF. Even if the files are edited to change the line endings, there are likely
208    some failures.    to be some failures. With --enable-newline-is-anycrlf or
209      --enable-newline-is-any, many tests should succeed, but there may be some
210      failures.
211    
212    . By default, the sequence \R in a pattern matches any Unicode line ending
213      sequence. This is independent of the option specifying what PCRE considers to
214      be the end of a line (see above). However, the caller of PCRE can restrict \R
215      to match only CR, LF, or CRLF. You can make this the default by adding
216      --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
217    
218  . When called via the POSIX interface, PCRE uses malloc() to get additional  . When called via the POSIX interface, PCRE uses malloc() to get additional
219    storage for processing capturing parentheses if there are more than 10 of    storage for processing capturing parentheses if there are more than 10 of
220    them. You can increase this threshold by setting, for example,    them in a pattern. You can increase this threshold by setting, for example,
221    
222    --with-posix-malloc-threshold=20    --with-posix-malloc-threshold=20
223    
# Line 147  library. You can read more about them in Line 230  library. You can read more about them in
230    --with-match-limit=500000    --with-match-limit=500000
231    
232    on the "configure" command. This is just the default; individual calls to    on the "configure" command. This is just the default; individual calls to
233    pcre_exec() can supply their own value. There is discussion on the pcreapi    pcre_exec() can supply their own value. There is more discussion on the
234    man page.    pcreapi man page.
235    
236  . There is a separate counter that limits the depth of recursive function calls  . There is a separate counter that limits the depth of recursive function calls
237    during a matching process. This also has a default of ten million, which is    during a matching process. This also has a default of ten million, which is
# Line 163  library. You can read more about them in Line 246  library. You can read more about them in
246  . The default maximum compiled pattern size is around 64K. You can increase  . The default maximum compiled pattern size is around 64K. You can increase
247    this by adding --with-link-size=3 to the "configure" command. You can    this by adding --with-link-size=3 to the "configure" command. You can
248    increase it even more by setting --with-link-size=4, but this is unlikely    increase it even more by setting --with-link-size=4, but this is unlikely
249    ever to be necessary. If you build PCRE with an increased link size, test 2    ever to be necessary. Increasing the internal link size will reduce
250    (and 5 if you are using UTF-8) will fail. Part of the output of these tests    performance.
   is a representation of the compiled pattern, and this changes with the link  
   size.  
251    
252  . You can build PCRE so that its internal match() function that is called from  . You can build PCRE so that its internal match() function that is called from
253    pcre_exec() does not call itself recursively. Instead, it uses blocks of data    pcre_exec() does not call itself recursively. Instead, it uses memory blocks
254    from the heap via special functions pcre_stack_malloc() and pcre_stack_free()    obtained from the heap via the special functions pcre_stack_malloc() and
255    to save data that would otherwise be saved on the stack. To build PCRE like    pcre_stack_free() to save data that would otherwise be saved on the stack. To
256    this, use    build PCRE like this, use
257    
258    --disable-stack-for-recursion    --disable-stack-for-recursion
259    
260    on the "configure" command. PCRE runs more slowly in this mode, but it may be    on the "configure" command. PCRE runs more slowly in this mode, but it may be
261    necessary in environments with limited stack sizes. This applies only to the    necessary in environments with limited stack sizes. This applies only to the
262    pcre_exec() function; it does not apply to pcre_dfa_exec(), which does not    normal execution of the pcre_exec() function; if JIT support is being
263    use deeply nested recursion.    successfully used, it is not relevant. Equally, it does not apply to
264      pcre_dfa_exec(), which does not use deeply nested recursion. There is a
265  The "configure" script builds eight files for the basic C library:    discussion about stack sizes in the pcrestack man page.
266    
267  . Makefile is the makefile that builds the library  . For speed, PCRE uses four tables for manipulating and identifying characters
268  . config.h contains build-time configuration options for the library    whose code point values are less than 256. By default, it uses a set of
269  . pcre-config is a script that shows the settings of "configure" options    tables for ASCII encoding that is part of the distribution. If you specify
270  . libpcre.pc is data for the pkg-config command  
271  . libtool is a script that builds shared and/or static libraries    --enable-rebuild-chartables
272  . RunTest is a script for running tests on the library  
273  . RunGrepTest is a script for running tests on the pcregrep command    a program called dftables is compiled and run in the default C locale when
274      you obey "make". It builds a source file called pcre_chartables.c. If you do
275  In addition, if a C++ compiler is found, the following are also built:    not specify this option, pcre_chartables.c is created as a copy of
276      pcre_chartables.c.dist. See "Character tables" below for further information.
277  . pcrecpp.h is the header file for programs that call PCRE via the C++ wrapper  
278  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions  . It is possible to compile PCRE for use on systems that use EBCDIC as their
279      character code (as opposed to ASCII) by specifying
280    
281      --enable-ebcdic
282    
283      This automatically implies --enable-rebuild-chartables (see above). However,
284      when PCRE is built this way, it always operates in EBCDIC. It cannot support
285      both EBCDIC and UTF-8.
286    
287    . It is possible to compile pcregrep to use libz and/or libbz2, in order to
288      read .gz and .bz2 files (respectively), by specifying one or both of
289    
290      --enable-pcregrep-libz
291      --enable-pcregrep-libbz2
292    
293      Of course, the relevant libraries must be installed on your system.
294    
295    . The default size of internal buffer used by pcregrep can be set by, for
296      example:
297    
298      --with-pcregrep-bufsize=50K
299    
300      The default value is 20K.
301    
302    . It is possible to compile pcretest so that it links with the libreadline
303      library, by specifying
304    
305      --enable-pcretest-libreadline
306    
307      If this is done, when pcretest's input is from a terminal, it reads it using
308      the readline() function. This provides line-editing and history facilities.
309      Note that libreadline is GPL-licenced, so if you distribute a binary of
310      pcretest linked in this way, there may be licensing issues.
311    
312      Setting this option causes the -lreadline option to be added to the pcretest
313      build. In many operating environments with a sytem-installed readline
314      library this is sufficient. However, in some environments (e.g. if an
315      unmodified distribution version of readline is in use), it may be necessary
316      to specify something like LIBS="-lncurses" as well. This is because, to quote
317      the readline INSTALL, "Readline uses the termcap functions, but does not link
318      with the termcap or curses library itself, allowing applications which link
319      with readline the to choose an appropriate library." If you get error
320      messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,
321      this is the problem, and linking with the ncurses library should fix it.
322    
323    The "configure" script builds the following files for the basic C library:
324    
325    . Makefile             the makefile that builds the library
326    . config.h             build-time configuration options for the library
327    . pcre.h               the public PCRE header file
328    . pcre-config          script that shows the building settings such as CFLAGS
329                             that were set for "configure"
330    . libpcre.pc         ) data for the pkg-config command
331    . libpcreposix.pc    )
332    . libtool              script that builds shared and/or static libraries
333    . RunTest              script for running tests on the basic C library
334    . RunGrepTest          script for running tests on the pcregrep command
335    
336    Versions of config.h and pcre.h are distributed in the PCRE tarballs under the
337    names config.h.generic and pcre.h.generic. These are provided for those who
338    have to built PCRE without using "configure" or CMake. If you use "configure"
339    or CMake, the .generic versions are not used.
340    
341    If a C++ compiler is found, the following files are also built:
342    
343    . libpcrecpp.pc        data for the pkg-config command
344    . pcrecpparg.h         header file for calling PCRE via the C++ wrapper
345    . pcre_stringpiece.h   header for the C++ "stringpiece" functions
346    
347  The "configure" script also creates config.status, which is an executable  The "configure" script also creates config.status, which is an executable
348  script that can be run to recreate the configuration, and config.log, which  script that can be run to recreate the configuration, and config.log, which
# Line 202  contains compiler output from tests that Line 350  contains compiler output from tests that
350    
351  Once "configure" has run, you can run "make". It builds two libraries, called  Once "configure" has run, you can run "make". It builds two libraries, called
352  libpcre and libpcreposix, a test program called pcretest, and the pcregrep  libpcre and libpcreposix, a test program called pcretest, and the pcregrep
353  command. If a C++ compiler was found on your system, it also builds the C++  command. If a C++ compiler was found on your system, and you did not disable it
354  wrapper library, which is called libpcrecpp, and some test programs called  with --disable-cpp, "make" also builds the C++ wrapper library, which is called
355  pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.  libpcrecpp, and some test programs called pcrecpp_unittest,
356    pcre_scanner_unittest, and pcre_stringpiece_unittest. If you enabled JIT
357  The command "make test" runs all the appropriate tests. Details of the PCRE  support with --enable-jit, a test program called pcre_jit_test is also built.
358  tests are given in a separate section of this document, below.  
359    The command "make check" runs all the appropriate tests. Details of the PCRE
360  You can use "make install" to copy the libraries, the public header files  tests are given below in a separate section of this document.
361  pcre.h, pcreposix.h, pcrecpp.h, and pcre_stringpiece.h (the last two only if  
362  the C++ wrapper was built), and the man pages to appropriate live directories  You can use "make install" to install PCRE into live directories on your
363  on your system, in the normal way.  system. The following are installed (file names are all relative to the
364    <prefix> that is set when "configure" is run):
365    
366      Commands (bin):
367        pcretest
368        pcregrep
369        pcre-config
370    
371      Libraries (lib):
372        libpcre
373        libpcreposix
374        libpcrecpp (if C++ support is enabled)
375    
376      Configuration information (lib/pkgconfig):
377        libpcre.pc
378        libpcreposix.pc
379        libpcrecpp.pc (if C++ support is enabled)
380    
381      Header files (include):
382        pcre.h
383        pcreposix.h
384        pcre_scanner.h      )
385        pcre_stringpiece.h  ) if C++ support is enabled
386        pcrecpp.h           )
387        pcrecpparg.h        )
388    
389      Man pages (share/man/man{1,3}):
390        pcregrep.1
391        pcretest.1
392        pcre-config.1
393        pcre.3
394        pcre*.3 (lots more pages, all starting "pcre")
395    
396      HTML documentation (share/doc/pcre/html):
397        index.html
398        *.html (lots more pages, hyperlinked from index.html)
399    
400      Text file documentation (share/doc/pcre):
401        AUTHORS
402        COPYING
403        ChangeLog
404        LICENCE
405        NEWS
406        README
407        pcre.txt         (a concatenation of the man(3) pages)
408        pcretest.txt     the pcretest man page
409        pcregrep.txt     the pcregrep man page
410        pcre-config.txt  the pcre-config man page
411    
412  If you want to remove PCRE from your system, you can run "make uninstall".  If you want to remove PCRE from your system, you can run "make uninstall".
413  This removes all the files that "make install" installed. However, it does not  This removes all the files that "make install" installed. However, it does not
# Line 222  remove any directories, because these ar Line 417  remove any directories, because these ar
417  Retrieving configuration information on Unix-like systems  Retrieving configuration information on Unix-like systems
418  ---------------------------------------------------------  ---------------------------------------------------------
419    
420  Running "make install" also installs the command pcre-config, which can be used  Running "make install" installs the command pcre-config, which can be used to
421  to recall information about the PCRE configuration and installation. For  recall information about the PCRE configuration and installation. For example:
 example:  
422    
423    pcre-config --version    pcre-config --version
424    
# Line 243  single command is used. For example: Line 437  single command is used. For example:
437    pkg-config --cflags pcre    pkg-config --cflags pcre
438    
439  The data is held in *.pc files that are installed in a directory called  The data is held in *.pc files that are installed in a directory called
440  pkgconfig.  <prefix>/lib/pkgconfig.
441    
442    
443  Shared libraries on Unix-like systems  Shared libraries on Unix-like systems
# Line 260  built. The programs pcretest and pcregre Line 454  built. The programs pcretest and pcregre
454  libraries (by means of wrapper scripts in the case of shared libraries). When  libraries (by means of wrapper scripts in the case of shared libraries). When
455  you use "make install" to install shared libraries, pcregrep and pcretest are  you use "make install" to install shared libraries, pcregrep and pcretest are
456  automatically re-built to use the newly installed shared libraries before being  automatically re-built to use the newly installed shared libraries before being
457  installed themselves. However, the versions left in the source directory still  installed themselves. However, the versions left in the build directory still
458  use the uninstalled libraries.  use the uninstalled libraries.
459    
460  To build PCRE using static libraries only you must use --disable-shared when  To build PCRE using static libraries only you must use --disable-shared when
# Line 272  Then run "make" in the usual way. Simila Line 466  Then run "make" in the usual way. Simila
466  build only shared libraries.  build only shared libraries.
467    
468    
469  Cross-compiling on a Unix-like system  Cross-compiling on Unix-like systems
470  -------------------------------------  ------------------------------------
471    
472  You can specify CC and CFLAGS in the normal way to the "configure" command, in  You can specify CC and CFLAGS in the normal way to the "configure" command, in
473  order to cross-compile PCRE for some other host. However, during the building  order to cross-compile PCRE for some other host. However, you should NOT
474  process, the dftables.c source file is compiled *and run* on the local host, in  specify --enable-rebuild-chartables, because if you do, the dftables.c source
475  order to generate the default character tables (the chartables.c file). It  file is compiled and run on the local host, in order to generate the inbuilt
476  therefore needs to be compiled with the local compiler, not the cross compiler.  character tables (the pcre_chartables.c file). This will probably not work,
477  You can do this by specifying CC_FOR_BUILD (and if necessary CFLAGS_FOR_BUILD;  because dftables.c needs to be compiled with the local compiler, not the cross
478  there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)  compiler.
479  when calling the "configure" command. If they are not specified, they default  
480  to the values of CC and CFLAGS.  When --enable-rebuild-chartables is not specified, pcre_chartables.c is created
481    by making a copy of pcre_chartables.c.dist, which is a default set of tables
482    that assumes ASCII code. Cross-compiling with the default tables should not be
483    a problem.
484    
485    If you need to modify the character tables when cross-compiling, you should
486    move pcre_chartables.c.dist out of the way, then compile dftables.c by hand and
487    run it on the local host to make a new version of pcre_chartables.c.dist.
488    Then when you cross-compile PCRE this new version of the tables will be used.
489    
490    
491  Using HP's ANSI C++ compiler (aCC)  Using HP's ANSI C++ compiler (aCC)
492  ----------------------------------  ----------------------------------
493    
494  Unless C++ support is disabled by specifying the "--disable-cpp" option of the  Unless C++ support is disabled by specifying the "--disable-cpp" option of the
495  "configure" script, you *must* include the "-AA" option in the CXXFLAGS  "configure" script, you must include the "-AA" option in the CXXFLAGS
496  environment variable in order for the C++ components to compile correctly.  environment variable in order for the C++ components to compile correctly.
497    
498  Also, note that the aCC compiler on PA-RISC platforms may have a defect whereby  Also, note that the aCC compiler on PA-RISC platforms may have a defect whereby
# Line 302  running the "configure" script: Line 504  running the "configure" script:
504    CXXLDFLAGS="-lstd_v2 -lCsup_v2"    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
505    
506    
507  Building on non-Unix systems  Using Sun's compilers for Solaris
508  ----------------------------  ---------------------------------
509    
510    A user reports that the following configurations work on Solaris 9 sparcv9 and
511    Solaris 9 x86 (32-bit):
512    
513      Solaris 9 sparcv9: ./configure --disable-cpp CC=/bin/cc CFLAGS="-m64 -g"
514      Solaris 9 x86:     ./configure --disable-cpp CC=/bin/cc CFLAGS="-g"
515    
516    
517    Using PCRE from MySQL
518    ---------------------
519    
520    On systems where both PCRE and MySQL are installed, it is possible to make use
521    of PCRE from within MySQL, as an alternative to the built-in pattern matching.
522    There is a web page that tells you how to do this:
523    
524      http://www.mysqludf.org/lib_mysqludf_preg/index.php
525    
526    
527    Making new tarballs
528    -------------------
529    
530    The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
531    zip formats. The command "make distcheck" does the same, but then does a trial
532    build of the new distribution to ensure that it works.
533    
534  For a non-Unix system, read the comments in the file NON-UNIX-USE, though if  If you have modified any of the man page sources in the doc directory, you
535  the system supports the use of "configure" and "make" you may be able to build  should first run the PrepareRelease script before making a distribution. This
536  PCRE in the same way as for Unix systems.  script creates the .txt and HTML forms of the documentation from the man pages.
   
 PCRE has been compiled on Windows systems and on Macintoshes, but I don't know  
 the details because I don't use those systems. It should be straightforward to  
 build PCRE on any system that has a Standard C compiler and library, because it  
 uses only Standard C functions.  
537    
538    
539  Testing PCRE  Testing PCRE
540  ------------  ------------
541    
542  To test PCRE on a Unix system, run the RunTest script that is created by the  To test the basic PCRE library on a Unix system, run the RunTest script that is
543  configuring process. There is also a script called RunGrepTest that tests the  created by the configuring process. There is also a script called RunGrepTest
544  options of the pcregrep command. If the C++ wrapper library is build, three  that tests the options of the pcregrep command. If the C++ wrapper library is
545  test programs called pcrecpp_unittest, pcre_scanner_unittest, and  built, three test programs called pcrecpp_unittest, pcre_scanner_unittest, and
546  pcre_stringpiece_unittest are provided.  pcre_stringpiece_unittest are also built. When JIT support is enabled, another
547    test program called pcre_jit_test is built.
548  Both the scripts and all the program tests are run if you obey "make runtest",  
549  "make check", or "make test". For other systems, see the instructions in  Both the scripts and all the program tests are run if you obey "make check" or
550  NON-UNIX-USE.  "make test". For other systems, see the instructions in NON-UNIX-USE.
551    
552  The RunTest script runs the pcretest test program (which is documented in its  The RunTest script runs the pcretest test program (which is documented in its
553  own man page) on each of the testinput files (in the testdata directory) in  own man page) on each of the relevant testinput files in the testdata
554  turn, and compares the output with the contents of the corresponding testoutput  directory, and compares the output with the contents of the corresponding
555  files. A file called testtry is used to hold the main output from pcretest  testoutput files. Some tests are relevant only when certain build-time options
556    were selected. For example, the tests for UTF-8 support are run only if
557    --enable-utf8 was used. RunTest outputs a comment when it skips a test.
558    
559    Many of the tests that are not skipped are run up to three times. The second
560    run forces pcre_study() to be called for all patterns except for a few in some
561    tests that are marked "never study" (see the pcretest program for how this is
562    done). If JIT support is available, the non-DFA tests are run a third time,
563    this time with a forced pcre_study() with the PCRE_STUDY_JIT_COMPILE option.
564    
565    RunTest uses a file called testtry to hold the main output from pcretest
566  (testsavedregex is also used as a working file). To run pcretest on just one of  (testsavedregex is also used as a working file). To run pcretest on just one of
567  the test files, give its number as an argument to RunTest, for example:  the test files, give its number as an argument to RunTest, for example:
568    
569    RunTest 2    RunTest 2
570    
571  The first test file can also be fed directly into the perltest script to check  The first test file can be fed directly into the perltest.pl script to check
572  that Perl gives the same results. The only difference you should see is in the  that Perl gives the same results. The only difference you should see is in the
573  first few lines, where the Perl version is given instead of the PCRE version.  first few lines, where the Perl version is given instead of the PCRE version.
574    
575  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),
576  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
577  detection, and run-time flags that are specific to PCRE, as well as the POSIX  detection, and run-time flags that are specific to PCRE, as well as the POSIX
578  wrapper API. It also uses the debugging flag to check some of the internals of  wrapper API. It also uses the debugging flags to check some of the internals of
579  pcre_compile().  pcre_compile().
580    
581  If you build PCRE with a locale setting that is not the standard C locale, the  If you build PCRE with a locale setting that is not the standard C locale, the
# Line 370  is output to say why. If running this te Line 601  is output to say why. If running this te
601  in the comparison output, it means that locale is not available on your system,  in the comparison output, it means that locale is not available on your system,
602  despite being listed by "locale". This does not mean that PCRE is broken.  despite being listed by "locale". This does not mean that PCRE is broken.
603    
604  The fourth test checks the UTF-8 support. It is not run automatically unless  [If you are trying to run this test on Windows, you may be able to get it to
605  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when  work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
606  running "configure". This file can be also fed directly to the perltest script,  RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
607  provided you are running Perl 5.8 or higher. (For Perl 5.6, a small patch,  Windows versions of test 2. More info on using RunTest.bat is included in the
608  commented in the script, can be be used.)  document entitled NON-UNIX-USE.]
609    
610    The fourth test checks the UTF-8 support. This file can be also fed directly to
611    the perltest.pl script, provided you are running Perl 5.8 or higher.
612    
613  The fifth test checks error handling with UTF-8 encoding, and internal UTF-8  The fifth test checks error handling with UTF-8 encoding, and internal UTF-8
614  features of PCRE that are not relevant to Perl.  features of PCRE that are not relevant to Perl.
615    
616  The sixth and test checks the support for Unicode character properties. It it  The sixth test (which is Perl-5.10 compatible) checks the support for Unicode
617  not run automatically unless PCRE is built with Unicode property support. To to  character properties. This file can be also fed directly to the perltest.pl
618  this you must set --enable-unicode-properties when running "configure".  script, provided you are running Perl 5.10 or higher.
619    
620  The seventh, eighth, and ninth tests check the pcre_dfa_exec() alternative  The seventh, eighth, and ninth tests check the pcre_dfa_exec() alternative
621  matching function, in non-UTF-8 mode, UTF-8 mode, and UTF-8 mode with Unicode  matching function, in non-UTF-8 mode, UTF-8 mode, and UTF-8 mode with Unicode
622  property support, respectively. The eighth and ninth tests are not run  property support, respectively.
623  automatically unless PCRE is build with the relevant support.  
624    The tenth test checks some internal offsets and code size features; it is run
625    only when the default "link size" of 2 is set (in other cases the sizes
626    change) and when Unicode property support is enabled.
627    
628    The eleventh and twelfth tests check out features that are new in Perl 5.10,
629    without and with UTF-8 support, respectively. This file can be also fed
630    directly to the perltest.pl script, provided you are running Perl 5.10 or
631    higher.
632    
633    The thirteenth test checks a number internals and non-Perl features concerned
634    with Unicode property support.
635    
636    The fourteenth test is run only when JIT support is available, and the
637    fifteenth test is run only when JIT support is not available. They test some
638    JIT-specific features such as information output from pcretest about JIT
639    compilation.
640    
641    
642  Character tables  Character tables
643  ----------------  ----------------
644    
645  PCRE uses four tables for manipulating and identifying characters whose values  For speed, PCRE uses four tables for manipulating and identifying characters
646  are less than 256. The final argument of the pcre_compile() function is a  whose code point values are less than 256. The final argument of the
647  pointer to a block of memory containing the concatenated tables. A call to  pcre_compile() function is a pointer to a block of memory containing the
648  pcre_maketables() can be used to generate a set of tables in the current  concatenated tables. A call to pcre_maketables() can be used to generate a set
649  locale. If the final argument for pcre_compile() is passed as NULL, a set of  of tables in the current locale. If the final argument for pcre_compile() is
650  default tables that is built into the binary is used.  passed as NULL, a set of default tables that is built into the binary is used.
651    
652  The source file called chartables.c contains the default set of tables. This is  The source file called pcre_chartables.c contains the default set of tables. By
653  not supplied in the distribution, but is built by the program dftables  default, this is created as a copy of pcre_chartables.c.dist, which contains
654  (compiled from dftables.c), which uses the ANSI C character handling functions  tables for ASCII coding. However, if --enable-rebuild-chartables is specified
655  such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table  for ./configure, a different version of pcre_chartables.c is built by the
656  sources. This means that the default C locale which is set for your system will  program dftables (compiled from dftables.c), which uses the ANSI C character
657  control the contents of these default tables. You can change the default tables  handling functions such as isalnum(), isalpha(), isupper(), islower(), etc. to
658  by editing chartables.c and then re-building PCRE. If you do this, you should  build the table sources. This means that the default C locale which is set for
659  probably also edit Makefile to ensure that the file doesn't ever get  your system will control the contents of these default tables. You can change
660  re-generated.  the default tables by editing pcre_chartables.c and then re-building PCRE. If
661    you do this, you should take care to ensure that the file does not get
662    automatically re-generated. The best way to do this is to move
663    pcre_chartables.c.dist out of the way and replace it with your customized
664    tables.
665    
666    When the dftables program is run as a result of --enable-rebuild-chartables,
667    it uses the default C locale that is set on your system. It does not pay
668    attention to the LC_xxx environment variables. In other words, it uses the
669    system's default locale rather than whatever the compiling user happens to have
670    set. If you really do want to build a source set of character tables in a
671    locale that is specified by the LC_xxx variables, you can run the dftables
672    program by hand with the -L option. For example:
673    
674      ./dftables -L pcre_chartables.c.special
675    
676  The first two 256-byte tables provide lower casing and case flipping functions,  The first two 256-byte tables provide lower casing and case flipping functions,
677  respectively. The next table consists of three 32-byte bit maps which identify  respectively. The next table consists of three 32-byte bit maps which identify
678  digits, "word" characters, and white space, respectively. These are used when  digits, "word" characters, and white space, respectively. These are used when
679  building 32-byte bit maps that represent character classes.  building 32-byte bit maps that represent character classes for code points less
680    than 256.
681    
682  The final 256-byte table has bits indicating various character types, as  The final 256-byte table has bits indicating various character types, as
683  follows:  follows:
# Line 428  You should not alter the set of characte Line 693  You should not alter the set of characte
693  will cause PCRE to malfunction.  will cause PCRE to malfunction.
694    
695    
696  Manifest  File manifest
697  --------  -------------
698    
699  The distribution should contain the following files:  The distribution should contain the following files:
700    
701  (A) The actual source files of the PCRE library functions and their  (A) Source files of the PCRE library functions and their headers:
     headers:  
702    
703    dftables.c            auxiliary program for building chartables.c    dftables.c              auxiliary program for building pcre_chartables.c
704                                when --enable-rebuild-chartables is specified
705    
706    pcreposix.c           )    pcre_chartables.c.dist  a default set of character tables that assume ASCII
707    pcre_compile.c        )                              coding; used, unless --enable-rebuild-chartables is
708    pcre_config.c         )                              specified, by copying to pcre_chartables.c
709    pcre_dfa_exec.c       )  
710    pcre_exec.c           )    pcreposix.c             )
711    pcre_fullinfo.c       )    pcre_compile.c          )
712    pcre_get.c            ) sources for the functions in the library,    pcre_config.c           )
713    pcre_globals.c        )   and some internal functions that they use    pcre_dfa_exec.c         )
714    pcre_info.c           )    pcre_exec.c             )
715    pcre_maketables.c     )    pcre_fullinfo.c         )
716    pcre_newline.c        )    pcre_get.c              ) sources for the functions in the library,
717    pcre_ord2utf8.c       )    pcre_globals.c          )   and some internal functions that they use
718    pcre_refcount.c       )    pcre_info.c             )
719    pcre_study.c          )    pcre_jit_compile.c      )
720    pcre_tables.c         )    pcre_maketables.c       )
721    pcre_try_flipped.c    )    pcre_newline.c          )
722    pcre_ucp_searchfuncs.c)    pcre_ord2utf8.c         )
723    pcre_valid_utf8.c     )    pcre_refcount.c         )
724    pcre_version.c        )    pcre_study.c            )
725    pcre_xclass.c         )    pcre_tables.c           )
726      pcre_try_flipped.c      )
727    pcre_printint.src     ) debugging function that is #included in pcretest, and    pcre_ucd.c              )
728                          )   can also be #included in pcre_compile()    pcre_valid_utf8.c       )
729      pcre_version.c          )
730    pcre.h                the public PCRE header file    pcre_xclass.c           )
731    pcreposix.h           header for the external POSIX wrapper API    pcre_printint.src       ) debugging function that is #included in pcretest,
732    pcre_internal.h       header for internal use                            )   and can also be #included in pcre_compile()
733    ucp.h                 ) headers concerned with    pcre.h.in               template for pcre.h when built by "configure"
734    ucpinternal.h         )   Unicode property handling    pcreposix.h             header for the external POSIX wrapper API
735    ucptable.h            ) (this one is the data table)    pcre_internal.h         header for internal use
736    config.in             template for config.h, which is built by configure    sljit/*                 16 files that make up the JIT compiler
737      ucp.h                   header for Unicode property handling
738    pcrecpp.h             the header file for the C++ wrapper  
739    pcrecpparg.h.in       "source" for another C++ header file    config.h.in             template for config.h, which is built by "configure"
740    pcrecpp.cc            )  
741    pcre_scanner.cc       ) source for the C++ wrapper library    pcrecpp.h               public header file for the C++ wrapper
742      pcrecpparg.h.in         template for another C++ header file
743    pcre_stringpiece.h.in "source" for pcre_stringpiece.h, the header for the    pcre_scanner.h          public header file for C++ scanner functions
744                            C++ stringpiece functions    pcrecpp.cc              )
745    pcre_stringpiece.cc   source for the C++ stringpiece functions    pcre_scanner.cc         ) source for the C++ wrapper library
746    
747  (B) Auxiliary files:    pcre_stringpiece.h.in   template for pcre_stringpiece.h, the header for the
748                                C++ stringpiece functions
749    AUTHORS               information about the author of PCRE    pcre_stringpiece.cc     source for the C++ stringpiece functions
750    ChangeLog             log of changes to the code  
751    INSTALL               generic installation instructions  (B) Source files for programs that use PCRE:
752    LICENCE               conditions for the use of PCRE  
753    COPYING               the same, using GNU's standard name    pcredemo.c              simple demonstration of coding calls to PCRE
754    Makefile.in           template for Unix Makefile, which is built by configure    pcregrep.c              source of a grep utility that uses PCRE
755    NEWS                  important changes in this release    pcretest.c              comprehensive test program
756    NON-UNIX-USE          notes on building PCRE on non-Unix systems  
757    README                this file  (C) Auxiliary files:
758    RunTest.in            template for a Unix shell script for running tests  
759    RunGrepTest.in        template for a Unix shell script for pcregrep tests    132html                 script to turn "man" pages into HTML
760    config.guess          ) files used by libtool,    AUTHORS                 information about the author of PCRE
761    config.sub            )   used only when building a shared library    ChangeLog               log of changes to the code
762    config.h.in           "source" for the config.h header file    CleanTxt                script to clean nroff output for txt man pages
763    configure             a configuring shell script (built by autoconf)    Detrail                 script to remove trailing spaces
764    configure.ac          the autoconf input used to build configure    HACKING                 some notes about the internals of PCRE
765    doc/Tech.Notes        notes on the encoding    INSTALL                 generic installation instructions
766    doc/*.3               man page sources for the PCRE functions    LICENCE                 conditions for the use of PCRE
767    doc/*.1               man page sources for pcregrep and pcretest    COPYING                 the same, using GNU's standard name
768    doc/html/*            HTML documentation    Makefile.in             ) template for Unix Makefile, which is built by
769    doc/pcre.txt          plain text version of the man pages                            )   "configure"
770    doc/pcretest.txt      plain text documentation of test program    Makefile.am             ) the automake input that was used to create
771    doc/perltest.txt      plain text documentation of Perl test program                            )   Makefile.in
772    install-sh            a shell script for installing files    NEWS                    important changes in this release
773    libpcre.pc.in         "source" for libpcre.pc for pkg-config    NON-UNIX-USE            notes on building PCRE on non-Unix systems
774    ltmain.sh             file used to build a libtool script    PrepareRelease          script to make preparations for "make dist"
775    mkinstalldirs         script for making install directories    README                  this file
776    pcretest.c            comprehensive test program    RunTest                 a Unix shell script for running tests
777    pcredemo.c            simple demonstration of coding calls to PCRE    RunGrepTest             a Unix shell script for pcregrep tests
778    perltest.pl           Perl test program    aclocal.m4              m4 macros (generated by "aclocal")
779    pcregrep.c            source of a grep utility that uses PCRE    config.guess            ) files used by libtool,
780    pcre-config.in        source of script which retains PCRE information    config.sub              )   used only when building a shared library
781    pcrecpp_unittest.c           )    configure               a configuring shell script (built by autoconf)
782    pcre_scanner_unittest.c      ) test programs for the C++ wrapper    configure.ac            ) the autoconf input that was used to build
783    pcre_stringpiece_unittest.c  )                            )   "configure" and config.h
784    testdata/testinput*   test data for main library tests    depcomp                 ) script to find program dependencies, generated by
785    testdata/testoutput*  expected test results                            )   automake
786    testdata/grep*        input and output for pcregrep tests    doc/*.3                 man page sources for PCRE
787      doc/*.1                 man page sources for pcregrep and pcretest
788      doc/index.html.src      the base HTML page
789      doc/html/*              HTML documentation
790      doc/pcre.txt            plain text version of the man pages
791      doc/pcretest.txt        plain text documentation of test program
792      doc/perltest.txt        plain text documentation of Perl test program
793      install-sh              a shell script for installing files
794      libpcre.pc.in           template for libpcre.pc for pkg-config
795      libpcreposix.pc.in      template for libpcreposix.pc for pkg-config
796      libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
797      ltmain.sh               file used to build a libtool script
798      missing                 ) common stub for a few missing GNU programs while
799                              )   installing, generated by automake
800      mkinstalldirs           script for making install directories
801      perltest.pl             Perl test program
802      pcre-config.in          source of script which retains PCRE information
803      pcre_jit_test.c         test program for the JIT compiler
804      pcrecpp_unittest.cc          )
805      pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
806      pcre_stringpiece_unittest.cc )
807      testdata/testinput*     test data for main library tests
808      testdata/testoutput*    expected test results
809      testdata/grep*          input and output for pcregrep tests
810    
811    (D) Auxiliary files for cmake support
812    
813      cmake/COPYING-CMAKE-SCRIPTS
814      cmake/FindPackageHandleStandardArgs.cmake
815      cmake/FindReadline.cmake
816      CMakeLists.txt
817      config-cmake.h.in
818    
819  (C) Auxiliary files for Win32 DLL  (E) Auxiliary files for VPASCAL
820    
821    libpcre.def    makevp.bat
822    libpcreposix.def    makevp_c.txt
823      makevp_l.txt
824      pcregexp.pas
825    
826  (D) Auxiliary file for VPASCAL  (F) Auxiliary files for building PCRE "by hand"
827    
828    makevp.bat    pcre.h.generic          ) a version of the public PCRE header file
829                              )   for use in non-"configure" environments
830      config.h.generic        ) a version of config.h for use in non-"configure"
831                              )   environments
832    
833    (F) Miscellaneous
834    
835      RunTest.bat            a script for running tests under Windows
836    
837  Philip Hazel  Philip Hazel
838  Email local part: ph10  Email local part: ph10
839  Email domain: cam.ac.uk  Email domain: cam.ac.uk
840  March 2007  Last updated: 23 August 2011

Legend:
Removed from v.99  
changed lines
  Added in v.672

  ViewVC Help
Powered by ViewVC 1.1.5