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

Diff of /code/trunk/README

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

revision 123 by ph10, Mon Mar 12 15:19:06 2007 UTC revision 1055 by chpe, Tue Oct 16 15:53:30 2012 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  There is a mailing list for discussion about the development of PCRE at
12    
# Line 15  The contents of this README file are: Line 18  The contents of this README file are:
18    The PCRE APIs    The PCRE APIs
19    Documentation for PCRE    Documentation for PCRE
20    Contributions by users of PCRE    Contributions by users of PCRE
21    Building PCRE on non-Unix systems    Building PCRE on non-Unix-like systems
22    Building PCRE on Unix-like systems    Building PCRE without using autotools
23    Retrieving configuration information on Unix-like systems    Building PCRE using autotools
24    Shared libraries on Unix-like systems    Retrieving configuration information
25    Cross-compiling on Unix-like systems    Shared libraries
26      Cross-compiling using autotools
27    Using HP's ANSI C++ compiler (aCC)    Using HP's ANSI C++ compiler (aCC)
28      Using PCRE from MySQL
29    Making new tarballs    Making new tarballs
30    Testing PCRE    Testing PCRE
31    Character tables    Character tables
# Line 30  The contents of this README file are: Line 35  The contents of this README file are:
35  The PCRE APIs  The PCRE APIs
36  -------------  -------------
37    
38  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. There are three sets of functions,
39  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page  one for the 8-bit library, which processes strings of bytes, one for the
40  for details).  16-bit library, which processes strings of 16-bit values, and one for the 32-bit
41    library, which processes strings of 32-bit values. The distribution also
42  Also included in the distribution are a set of C wrapper functions that are  includes a set of C++ wrapper functions (see the pcrecpp man page for details),
43  based on the POSIX API. These end up in the library called libpcreposix. Note  courtesy of Google Inc., which can be used to call the 8-bit PCRE library from
44  that this just provides a POSIX calling interface to PCRE; the regular  C++.
45  expressions themselves still follow Perl syntax and semantics. The POSIX API is  
46  restricted, and does not give full access to all of PCRE's facilities.  In addition, there is a set of C wrapper functions (again, just for the 8-bit
47    library) that are based on the POSIX regular expression API (see the pcreposix
48    man page). These end up in the library called libpcreposix. Note that this just
49    provides a POSIX calling interface to PCRE; the regular expressions themselves
50    still follow Perl syntax and semantics. The POSIX API is restricted, and does
51    not give full access to all of PCRE's facilities.
52    
53  The header file for the POSIX-style functions is called pcreposix.h. The  The header file for the POSIX-style functions is called pcreposix.h. The
54  official POSIX name is regex.h, but I did not want to risk possible problems  official POSIX name is regex.h, but I did not want to risk possible problems
# Line 81  documentation is supplied in two other f Line 91  documentation is supplied in two other f
91       in various ways, and rooted in a file called index.html, is distributed in       in various ways, and rooted in a file called index.html, is distributed in
92       doc/html and installed in <prefix>/share/doc/pcre/html.       doc/html and installed in <prefix>/share/doc/pcre/html.
93    
94    Users of PCRE have contributed files containing the documentation for various
95    releases in CHM format. These can be found in the Contrib directory of the FTP
96    site (see next section).
97    
98    
99  Contributions by users of PCRE  Contributions by users of PCRE
100  ------------------------------  ------------------------------
# Line 91  You can find contributions from PCRE use Line 105  You can find contributions from PCRE use
105    
106  There is a README file giving brief descriptions of what they are. Some are  There is a README file giving brief descriptions of what they are. Some are
107  complete in themselves; others are pointers to URLs containing relevant files.  complete in themselves; others are pointers to URLs containing relevant files.
108  Some of this material is likely to be well out-of-date. In particular, several  Some of this material is likely to be well out-of-date. Several of the earlier
109  of the contributions provide support for compiling PCRE on various flavours of  contributions provided support for compiling PCRE on various flavours of
110  Windows (I myself do not use Windows), but nowadays there is more Windows  Windows (I myself do not use Windows). Nowadays there is more Windows support
111  support in the standard distribution.  in the standard distribution, so these contibutions have been archived.
112    
113    
114  Building PCRE on non-Unix systems  Building PCRE on non-Unix-like systems
115  ---------------------------------  --------------------------------------
116    
117  For a non-Unix system, please read the comments in the file NON-UNIX-USE,  For a non-Unix-like system, please read the comments in the file
118  though if your system supports the use of "configure" and "make" you may be  NON-AUTOTOOLS-BUILD, though if your system supports the use of "configure" and
119  able to build PCRE in the same way as for Unix-like systems.  "make" you may be able to build PCRE using autotools in the same way as for
120    many Unix-like systems.
121    
122    PCRE can also be configured using the GUI facility provided by CMake's
123    cmake-gui command. This creates Makefiles, solution files, etc. The file
124    NON-AUTOTOOLS-BUILD has information about CMake.
125    
126  PCRE has been compiled on many different operating systems. It should be  PCRE has been compiled on many different operating systems. It should be
127  straightforward to build PCRE on any system that has a Standard C compiler and  straightforward to build PCRE on any system that has a Standard C compiler and
128  library, because it uses only Standard C functions.  library, because it uses only Standard C functions.
129    
130    
131  Building PCRE on Unix-like systems  Building PCRE without using autotools
132  ----------------------------------  -------------------------------------
133    
134    The use of autotools (in particular, libtool) is problematic in some
135    environments, even some that are Unix or Unix-like. See the NON-AUTOTOOLS-BUILD
136    file for ways of building PCRE without using autotools.
137    
138    
139    Building PCRE using autotools
140    -----------------------------
141    
142  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
143  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
144    
145  To build PCRE on a Unix-like system, first run the "configure" command from the  The following instructions assume the use of the widely used "configure; make;
146  PCRE distribution directory, with your current directory set to the directory  make install" (autotools) process.
147  where you want the files to be created. This command is a standard GNU  
148  "autoconf" configuration script, for which generic instructions are supplied in  To build PCRE on system that supports autotools, first run the "configure"
149  the file INSTALL.  command from the PCRE distribution directory, with your current directory set
150    to the directory where you want the files to be created. This command is a
151    standard GNU "autoconf" configuration script, for which generic instructions
152    are supplied in the file INSTALL.
153    
154  Most commonly, people build PCRE within its own distribution directory, and in  Most commonly, people build PCRE within its own distribution directory, and in
155  this case, on many systems, just running "./configure" is sufficient. However,  this case, on many systems, just running "./configure" is sufficient. However,
# Line 127  the usual methods of changing standard d Line 157  the usual methods of changing standard d
157    
158  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local  CFLAGS='-O2 -Wall' ./configure --prefix=/opt/local
159    
160  specifies that the C compiler should be run with the flags '-O2 -Wall' instead  This command specifies that the C compiler should be run with the flags '-O2
161  of the default, and that "make install" should install PCRE under /opt/local  -Wall' instead of the default, and that "make install" should install PCRE
162  instead of the default /usr/local.  under /opt/local instead of the default /usr/local.
163    
164  If you want to build in a different directory, just run "configure" with that  If you want to build in a different directory, just run "configure" with that
165  directory as current. For example, suppose you have unpacked the PCRE source  directory as current. For example, suppose you have unpacked the PCRE source
# Line 143  possible to build it as a C++ library, t Line 173  possible to build it as a C++ library, t
173  does not have any features to support this.  does not have any features to support this.
174    
175  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
176  library. You can read more about them in the pcrebuild man page.  library. They are also documented in the pcrebuild man page.
177    
178    . By default, both shared and static libraries are built. You can change this
179      by adding one of these options to the "configure" command:
180    
181  . If you want to suppress the building of the C++ wrapper library, you can add    --disable-shared
182    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,    --disable-static
183    will try to find a C++ compiler and C++ header files, and if it succeeds, it  
184    will try to build the C++ wrapper.    (See also "Shared libraries on Unix-like systems" below.)
185    
186  . If you want to make use of the support for UTF-8 character strings in PCRE,  . By default, only the 8-bit library is built. If you add --enable-pcre16 to
187    you must add --enable-utf8 to the "configure" command. Without it, the code    the "configure" command, the 16-bit library is also built. If you add
188    for handling UTF-8 is not included in the library. (Even when included, it    --enable-pcre32 to the "configure" command, the 32-bit library is also built.
189    still has to be enabled by an option at run time.)    If you want only the 16-bit or 32-bit library, --disable-pcre8 to disable
190      building the 8-bit library.
191  . If, in addition to support for UTF-8 character strings, you want to include  
192    support for the \P, \p, and \X sequences that recognize Unicode character  . If you are building the 8-bit library and want to suppress the building of
193    properties, you must add --enable-unicode-properties to the "configure"    the C++ wrapper library, you can add --disable-cpp to the "configure"
194    command. This adds about 30K to the size of the library (in the form of a    command. Otherwise, when "configure" is run without --disable-pcre8, it will
195    property table); only the basic two-letter properties such as Lu are    try to find a C++ compiler and C++ header files, and if it succeeds, it will
196    supported.    try to build the C++ wrapper.
197    
198    . If you want to include support for just-in-time compiling, which can give
199      large performance improvements on certain platforms, add --enable-jit to the
200      "configure" command. This support is available only for certain hardware
201      architectures. If you try to enable it on an unsupported architecture, there
202      will be a compile time error.
203    
204    . When JIT support is enabled, pcregrep automatically makes use of it, unless
205      you add --disable-pcregrep-jit to the "configure" command.
206    
207    . If you want to make use of the support for UTF-8 Unicode character strings in
208      the 8-bit library, or UTF-16 Unicode character strings in the 16-bit library,
209      or UTF-32 Unicode character strings in the 32-bit library, you must add
210      --enable-utf to the "configure" command. Without it, the code for handling
211      UTF-8, UTF-16 and UTF-8 is not included in the relevant library. Even
212      when --enable-utf is included, the use of a UTF encoding still has to be
213      enabled by an option at run time. When PCRE is compiled with this option, its
214      input can only either be ASCII or UTF-8/16/32, even when running on EBCDIC
215      platforms. It is not possible to use both --enable-utf and --enable-ebcdic at
216      the same time.
217    
218    . There are no separate options for enabling UTF-8, UTF-16 and UTF-32
219      independently because that would allow ridiculous settings such as requesting
220      UTF-16 support while building only the 8-bit library. However, the option
221      --enable-utf8 is retained for backwards compatibility with earlier releases
222      that did not support 16-bit or 32-bit character strings. It is synonymous with
223      --enable-utf. It is not possible to configure one library with UTF support
224      and the other without in the same configuration.
225    
226    . If, in addition to support for UTF-8/16/32 character strings, you want to
227      include support for the \P, \p, and \X sequences that recognize Unicode
228      character properties, you must add --enable-unicode-properties to the
229      "configure" command. This adds about 30K to the size of the library (in the
230      form of a property table); only the basic two-letter properties such as Lu
231      are supported.
232    
233  . 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
234    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
235    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
236    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
237    (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
238    --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
239    to the "configure" command, respectively.    or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
240      --enable-newline-is-any to the "configure" command, respectively.
241    If you specify --newline-is-cr or --newline-is-crlf, some of the standard  
242    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
243    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
244    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
245    some failures.    to be some failures. With --enable-newline-is-anycrlf or
246      --enable-newline-is-any, many tests should succeed, but there may be some
247      failures.
248    
249    . By default, the sequence \R in a pattern matches any Unicode line ending
250      sequence. This is independent of the option specifying what PCRE considers to
251      be the end of a line (see above). However, the caller of PCRE can restrict \R
252      to match only CR, LF, or CRLF. You can make this the default by adding
253      --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
254    
255  . When called via the POSIX interface, PCRE uses malloc() to get additional  . When called via the POSIX interface, PCRE uses malloc() to get additional
256    storage for processing capturing parentheses if there are more than 10 of    storage for processing capturing parentheses if there are more than 10 of
257    them. You can increase this threshold by setting, for example,    them in a pattern. You can increase this threshold by setting, for example,
258    
259    --with-posix-malloc-threshold=20    --with-posix-malloc-threshold=20
260    
# Line 205  library. You can read more about them in Line 281  library. You can read more about them in
281    sizes in the pcrestack man page.    sizes in the pcrestack man page.
282    
283  . The default maximum compiled pattern size is around 64K. You can increase  . The default maximum compiled pattern size is around 64K. You can increase
284    this by adding --with-link-size=3 to the "configure" command. You can    this by adding --with-link-size=3 to the "configure" command. In the 8-bit
285    increase it even more by setting --with-link-size=4, but this is unlikely    library, PCRE then uses three bytes instead of two for offsets to different
286    ever to be necessary.    parts of the compiled pattern. In the 16-bit library, --with-link-size=3 is
287      the same as --with-link-size=4, which (in both libraries) uses four-byte
288      offsets. Increasing the internal link size reduces performance. In the 32-bit
289      library, the only supported link size is 4.
290    
291  . 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
292    pcre_exec() does not call itself recursively. Instead, it uses memory blocks    pcre_exec() does not call itself recursively. Instead, it uses memory blocks
# Line 219  library. You can read more about them in Line 298  library. You can read more about them in
298    
299    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
300    necessary in environments with limited stack sizes. This applies only to the    necessary in environments with limited stack sizes. This applies only to the
301    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
302    use deeply nested recursion. There is a discussion about stack sizes in the    successfully used, it is not relevant. Equally, it does not apply to
303    pcrestack man page.    pcre_dfa_exec(), which does not use deeply nested recursion. There is a
304      discussion about stack sizes in the pcrestack man page.
305    
306    . For speed, PCRE uses four tables for manipulating and identifying characters
307      whose code point values are less than 256. By default, it uses a set of
308      tables for ASCII encoding that is part of the distribution. If you specify
309    
310      --enable-rebuild-chartables
311    
312      a program called dftables is compiled and run in the default C locale when
313      you obey "make". It builds a source file called pcre_chartables.c. If you do
314      not specify this option, pcre_chartables.c is created as a copy of
315      pcre_chartables.c.dist. See "Character tables" below for further information.
316    
317    . It is possible to compile PCRE for use on systems that use EBCDIC as their
318      character code (as opposed to ASCII/Unicode) by specifying
319    
320      --enable-ebcdic
321    
322      This automatically implies --enable-rebuild-chartables (see above). However,
323      when PCRE is built this way, it always operates in EBCDIC. It cannot support
324      both EBCDIC and UTF-8/16/32. There is a second option, --enable-ebcdic-nl25,
325      which specifies that the code value for the EBCDIC NL character is 0x25
326      instead of the default 0x15.
327    
328    . The pcregrep program currently supports only 8-bit data files, and so
329      requires the 8-bit PCRE library. It is possible to compile pcregrep to use
330      libz and/or libbz2, in order to read .gz and .bz2 files (respectively), by
331      specifying one or both of
332    
333      --enable-pcregrep-libz
334      --enable-pcregrep-libbz2
335    
336      Of course, the relevant libraries must be installed on your system.
337    
338    . The default size of internal buffer used by pcregrep can be set by, for
339      example:
340    
341      --with-pcregrep-bufsize=50K
342    
343      The default value is 20K.
344    
345    . It is possible to compile pcretest so that it links with the libreadline
346      or libedit libraries, by specifying, respectively,
347    
348      --enable-pcretest-libreadline or --enable-pcretest-libedit
349    
350      If this is done, when pcretest's input is from a terminal, it reads it using
351      the readline() function. This provides line-editing and history facilities.
352      Note that libreadline is GPL-licenced, so if you distribute a binary of
353      pcretest linked in this way, there may be licensing issues. These can be
354      avoided by linking with libedit (which has a BSD licence) instead.
355    
356      Enabling libreadline causes the -lreadline option to be added to the pcretest
357      build. In many operating environments with a sytem-installed readline
358      library this is sufficient. However, in some environments (e.g. if an
359      unmodified distribution version of readline is in use), it may be necessary
360      to specify something like LIBS="-lncurses" as well. This is because, to quote
361      the readline INSTALL, "Readline uses the termcap functions, but does not link
362      with the termcap or curses library itself, allowing applications which link
363      with readline the to choose an appropriate library." If you get error
364      messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,
365      this is the problem, and linking with the ncurses library should fix it.
366    
367  The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
368    
369  . Makefile is the makefile that builds the library  . Makefile             the makefile that builds the library
370  . config.h contains build-time configuration options for the library  . config.h             build-time configuration options for the library
371  . pcre.h is the public PCRE header file  . pcre.h               the public PCRE header file
372  . pcre-config is a script that shows the settings of "configure" options  . pcre-config          script that shows the building settings such as CFLAGS
373  . libpcre.pc is data for the pkg-config command                           that were set for "configure"
374  . libtool is a script that builds shared and/or static libraries  . libpcre.pc         ) data for the pkg-config command
375  . RunTest is a script for running tests on the basic C library  . libpcre16.pc       )
376  . RunGrepTest is a script for running tests on the pcregrep command  . libpcre32.pc       )
377    . libpcreposix.pc    )
378  Versions of config.h and pcre.h are distributed in the PCRE tarballs under  . libtool              script that builds shared and/or static libraries
379  the names config.h.generic and pcre.h.generic. These are provided for the  
380  benefit of those who have to built PCRE without the benefit of "configure". If  Versions of config.h and pcre.h are distributed in the PCRE tarballs under the
381  you use "configure", the .generic versions are not used.  names config.h.generic and pcre.h.generic. These are provided for those who
382    have to built PCRE without using "configure" or CMake. If you use "configure"
383  If a C++ compiler is found, the following files are also built:  or CMake, the .generic versions are not used.
384    
385  . libpcrecpp.pc is data for the pkg-config command  When building the 8-bit library, if a C++ compiler is found, the following
386  . pcrecpparg.h is a header file for programs that call PCRE via the C++ wrapper  files are also built:
387  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions  
388    . libpcrecpp.pc        data for the pkg-config command
389    . pcrecpparg.h         header file for calling PCRE via the C++ wrapper
390    . pcre_stringpiece.h   header for the C++ "stringpiece" functions
391    
392  The "configure" script also creates config.status, which is an executable  The "configure" script also creates config.status, which is an executable
393  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
394  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
395    
396  Once "configure" has run, you can run "make". It builds two libraries, called  Once "configure" has run, you can run "make". This builds the the libraries
397  libpcre and libpcreposix, a test program called pcretest, a demonstration  libpcre, libpcre16 and/or libpcre32, and a test program called pcretest. If you
398  program called pcredemo, and the pcregrep command. If a C++ compiler was found  enabled JIT support with --enable-jit, a test program called pcre_jit_test is
399  on your system, "make" also builds the C++ wrapper library, which is called  built as well.
400  libpcrecpp, and some test programs called pcrecpp_unittest,  
401  pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper  If the 8-bit library is built, libpcreposix and the pcregrep command are also
402  can be disabled by adding --disable-cpp to the "configure" command.  built, and if a C++ compiler was found on your system, and you did not disable
403    it with --disable-cpp, "make" builds the C++ wrapper library, which is called
404    libpcrecpp, as well as some test programs called pcrecpp_unittest,
405    pcre_scanner_unittest, and pcre_stringpiece_unittest.
406    
407  The command "make check" runs all the appropriate tests. Details of the PCRE  The command "make check" runs all the appropriate tests. Details of the PCRE
408  tests are given below in a separate section of this document.  tests are given below in a separate section of this document.
# Line 266  system. The following are installed (fil Line 413  system. The following are installed (fil
413    
414    Commands (bin):    Commands (bin):
415      pcretest      pcretest
416      pcregrep      pcregrep (if 8-bit support is enabled)
417      pcre-config      pcre-config
418    
419    Libraries (lib):    Libraries (lib):
420      libpcre      libpcre16     (if 16-bit support is enabled)
421      libpcreposix      libpcre32     (if 32-bit support is enabled)
422      libpcrecpp (if C++ support is enabled)      libpcre       (if 8-bit support is enabled)
423        libpcreposix  (if 8-bit support is enabled)
424        libpcrecpp    (if 8-bit and C++ support is enabled)
425    
426    Configuration information (lib/pkgconfig):    Configuration information (lib/pkgconfig):
427        libpcre16.pc
428        libpcre32.pc
429      libpcre.pc      libpcre.pc
430        libpcreposix.pc
431      libpcrecpp.pc (if C++ support is enabled)      libpcrecpp.pc (if C++ support is enabled)
432    
433    Header files (include):    Header files (include):
# Line 289  system. The following are installed (fil Line 441  system. The following are installed (fil
441    Man pages (share/man/man{1,3}):    Man pages (share/man/man{1,3}):
442      pcregrep.1      pcregrep.1
443      pcretest.1      pcretest.1
444        pcre-config.1
445      pcre.3      pcre.3
446      pcre*.3 (lots more pages, all starting "pcre")      pcre*.3 (lots more pages, all starting "pcre")
447    
# Line 303  system. The following are installed (fil Line 456  system. The following are installed (fil
456      LICENCE      LICENCE
457      NEWS      NEWS
458      README      README
459      pcre.txt       (a concatenation of the man(3) pages)      pcre.txt         (a concatenation of the man(3) pages)
460      pcretest.txt   the pcretest man page      pcretest.txt     the pcretest man page
461      pcregrep.txt   the pcregrep man page      pcregrep.txt     the pcregrep man page
462        pcre-config.txt  the pcre-config man page
 Note that the pcredemo program that is built by "configure" is *not* installed  
 anywhere. It is a demonstration for programmers wanting to use PCRE.  
463    
464  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".
465  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
466  remove any directories, because these are often shared with other programs.  remove any directories, because these are often shared with other programs.
467    
468    
469  Retrieving configuration information on Unix-like systems  Retrieving configuration information
470  ---------------------------------------------------------  ------------------------------------
471    
472  Running "make install" installs the command pcre-config, which can be used to  Running "make install" installs the command pcre-config, which can be used to
473  recall information about the PCRE configuration and installation. For example:  recall information about the PCRE configuration and installation. For example:
# Line 341  The data is held in *.pc files that are Line 492  The data is held in *.pc files that are
492  <prefix>/lib/pkgconfig.  <prefix>/lib/pkgconfig.
493    
494    
495  Shared libraries on Unix-like systems  Shared libraries
496  -------------------------------------  ----------------
497    
498  The default distribution builds PCRE as shared libraries and static libraries,  The default distribution builds PCRE as shared libraries and static libraries,
499  as long as the operating system supports shared libraries. Shared library  as long as the operating system supports shared libraries. Shared library
# Line 367  Then run "make" in the usual way. Simila Line 518  Then run "make" in the usual way. Simila
518  build only shared libraries.  build only shared libraries.
519    
520    
521  Cross-compiling on Unix-like systems  Cross-compiling using autotools
522  ------------------------------------  -------------------------------
523    
524  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
525  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
526  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
527  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
528  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,
529  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
530  there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)  compiler.
531  when calling the "configure" command. If they are not specified, they default  
532  to the values of CC and CFLAGS.  When --enable-rebuild-chartables is not specified, pcre_chartables.c is created
533    by making a copy of pcre_chartables.c.dist, which is a default set of tables
534    that assumes ASCII code. Cross-compiling with the default tables should not be
535    a problem.
536    
537    If you need to modify the character tables when cross-compiling, you should
538    move pcre_chartables.c.dist out of the way, then compile dftables.c by hand and
539    run it on the local host to make a new version of pcre_chartables.c.dist.
540    Then when you cross-compile PCRE this new version of the tables will be used.
541    
542    
543  Using HP's ANSI C++ compiler (aCC)  Using HP's ANSI C++ compiler (aCC)
# Line 397  running the "configure" script: Line 556  running the "configure" script:
556    CXXLDFLAGS="-lstd_v2 -lCsup_v2"    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
557    
558    
559    Using Sun's compilers for Solaris
560    ---------------------------------
561    
562    A user reports that the following configurations work on Solaris 9 sparcv9 and
563    Solaris 9 x86 (32-bit):
564    
565      Solaris 9 sparcv9: ./configure --disable-cpp CC=/bin/cc CFLAGS="-m64 -g"
566      Solaris 9 x86:     ./configure --disable-cpp CC=/bin/cc CFLAGS="-g"
567    
568    
569    Using PCRE from MySQL
570    ---------------------
571    
572    On systems where both PCRE and MySQL are installed, it is possible to make use
573    of PCRE from within MySQL, as an alternative to the built-in pattern matching.
574    There is a web page that tells you how to do this:
575    
576      http://www.mysqludf.org/lib_mysqludf_preg/index.php
577    
578    
579  Making new tarballs  Making new tarballs
580  -------------------  -------------------
581    
582  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
583  zip formats. However, if you have modified any of the man page sources in the  zip formats. The command "make distcheck" does the same, but then does a trial
584  doc directory, you should first run the PrepareRelease script. This re-creates  build of the new distribution to ensure that it works.
585  the .txt and HTML forms of the documentation from the man pages.  
586    If you have modified any of the man page sources in the doc directory, you
587    should first run the PrepareRelease script before making a distribution. This
588    script creates the .txt and HTML forms of the documentation from the man pages.
589    
590    
591  Testing PCRE  Testing PCRE
592  ------------  ------------
593    
594  To test the basic PCRE library on a Unix system, run the RunTest script that is  To test the basic PCRE library on a Unix-like system, run the RunTest script.
595  created by the configuring process. There is also a script called RunGrepTest  There is another script called RunGrepTest that tests the options of the
596  that tests the options of the pcregrep command. If the C++ wrapper library is  pcregrep command. If the C++ wrapper library is built, three test programs
597  built, three test programs called pcrecpp_unittest, pcre_scanner_unittest, and  called pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest
598  pcre_stringpiece_unittest are also built.  are also built. When JIT support is enabled, another test program called
599    pcre_jit_test is built.
600    
601  Both the scripts and all the program tests are run if you obey "make check" or  Both the scripts and all the program tests are run if you obey "make check" or
602  "make test". For other systems, see the instructions in NON-UNIX-USE.  "make test". For other environments, see the instructions in
603    NON-AUTOTOOLS-BUILD.
604    
605  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
606  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
607  turn, and compares the output with the contents of the corresponding testoutput  directory, and compares the output with the contents of the corresponding
608  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
609  (testsavedregex is also used as a working file). To run pcretest on just one of  were selected. For example, the tests for UTF-8/16/32 support are run only if
610  the test files, give its number as an argument to RunTest, for example:  --enable-utf was used. RunTest outputs a comment when it skips a test.
611    
612    RunTest 2  Many of the tests that are not skipped are run up to three times. The second
613    run forces pcre_study() to be called for all patterns except for a few in some
614  The first test file can also be fed directly into the perltest.pl script to  tests that are marked "never study" (see the pcretest program for how this is
615  check that Perl gives the same results. The only difference you should see is  done). If JIT support is available, the non-DFA tests are run a third time,
616  in the first few lines, where the Perl version is given instead of the PCRE  this time with a forced pcre_study() with the PCRE_STUDY_JIT_COMPILE option.
617  version.  
618    The entire set of tests is run once for each of the 8-bit, 16-bit and 32-bit
619    libraries that are enabled. If you want to run just one set of tests, call
620    RunTest with either the -8, -16 or -32 option.
621    
622    RunTest uses a file called testtry to hold the main output from pcretest.
623    Other files whose names begin with "test" are used as working files in some
624    tests. To run pcretest on just one or more specific test files, give their
625    numbers as arguments to RunTest, for example:
626    
627      RunTest 2 7 11
628    
629    You can also call RunTest with the single argument "list" to cause it to output
630    a list of tests.
631    
632    The first test file can be fed directly into the perltest.pl script to check
633    that Perl gives the same results. The only difference you should see is in the
634    first few lines, where the Perl version is given instead of the PCRE version.
635    
636  The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(),  The second set of tests check pcre_fullinfo(), pcre_study(),
637  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error  pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error
638  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
639  wrapper API. It also uses the debugging flags to check some of the internals of  wrapper API. It also uses the debugging flags to check some of the internals of
# Line 461  is output to say why. If running this te Line 662  is output to say why. If running this te
662  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,
663  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.
664    
665  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
666  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
667  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
668  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
669  commented in the script, can be be used.)  document entitled NON-UNIX-USE.]
670    
671  The fifth test checks error handling with UTF-8 encoding, and internal UTF-8  The fourth and fifth tests check the UTF-8/16/32 support and error handling and
672  features of PCRE that are not relevant to Perl.  internal UTF features of PCRE that are not relevant to Perl, respectively. The
673    sixth and seventh tests do the same for Unicode character properties support.
674  The sixth test checks the support for Unicode character properties. It it not  
675  run automatically unless PCRE is built with Unicode property support. To to  The eighth, ninth, and tenth tests check the pcre_dfa_exec() alternative
676  this you must set --enable-unicode-properties when running "configure".  matching function, in non-UTF-8/16/32 mode, UTF-8/16/32 mode, and UTF-8/16/32
677    mode with Unicode property support, respectively.
678  The seventh, eighth, and ninth tests check the pcre_dfa_exec() alternative  
679  matching function, in non-UTF-8 mode, UTF-8 mode, and UTF-8 mode with Unicode  The eleventh test checks some internal offsets and code size features; it is
680  property support, respectively. The eighth and ninth tests are not run  run only when the default "link size" of 2 is set (in other cases the sizes
681  automatically unless PCRE is build with the relevant support.  change) and when Unicode property support is enabled.
682    
683    The twelfth test is run only when JIT support is available, and the thirteenth
684    test is run only when JIT support is not available. They test some JIT-specific
685    features such as information output from pcretest about JIT compilation.
686    
687    The fourteenth, fifteenth, and sixteenth tests are run only in 8-bit mode, and
688    the seventeenth, eighteenth, and nineteenth tests are run only in 16/32-bit mode.
689    These are tests that generate different output in the two modes. They are for
690    general cases, UTF-8/16/32 support, and Unicode property support, respectively.
691    
692    The twentieth test is run only in 16/32-bit mode. It tests some specific
693    16/32-bit features of the DFA matching engine.
694    
695    The twenty-first and twenty-second tests are run only in 16/32-bit mode, when the
696    link size is set to 2 for the 16-bit library. They test reloading pre-compiled patterns.
697    
698    The twenty-third and twenty-fourth tests are run only in 16-bit mode. They are for
699    general cases, and UTF-16 support, respectively.
700    
701    The twenty-fifth and twenty-sixth tests are run only in 32-bit mode. They are for
702    general cases, and UTF-32 support, respectively.
703    
704  Character tables  Character tables
705  ----------------  ----------------
# Line 490  concatenated tables. A call to pcre_make Line 711  concatenated tables. A call to pcre_make
711  of tables in the current locale. If the final argument for pcre_compile() is  of tables in the current locale. If the final argument for pcre_compile() is
712  passed as NULL, a set of 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.
713    
714  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
715  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
716  (compiled from dftables.c), which uses the ANSI C character handling functions  tables for ASCII coding. However, if --enable-rebuild-chartables is specified
717  such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table  for ./configure, a different version of pcre_chartables.c is built by the
718  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
719  control the contents of these default tables. You can change the default tables  handling functions such as isalnum(), isalpha(), isupper(), islower(), etc. to
720  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
721  take care to ensure that the file does not get automaticaly re-generated.  your system will control the contents of these default tables. You can change
722    the default tables by editing pcre_chartables.c and then re-building PCRE. If
723    you do this, you should take care to ensure that the file does not get
724    automatically re-generated. The best way to do this is to move
725    pcre_chartables.c.dist out of the way and replace it with your customized
726    tables.
727    
728    When the dftables program is run as a result of --enable-rebuild-chartables,
729    it uses the default C locale that is set on your system. It does not pay
730    attention to the LC_xxx environment variables. In other words, it uses the
731    system's default locale rather than whatever the compiling user happens to have
732    set. If you really do want to build a source set of character tables in a
733    locale that is specified by the LC_xxx variables, you can run the dftables
734    program by hand with the -L option. For example:
735    
736      ./dftables -L pcre_chartables.c.special
737    
738  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,
739  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
# Line 522  will cause PCRE to malfunction. Line 758  will cause PCRE to malfunction.
758  File manifest  File manifest
759  -------------  -------------
760    
761  The distribution should contain the following files:  The distribution should contain the files listed below. Where a file name is
762    given as pcre[16|32]_xxx it means that there are three files, one with the name
763    pcre_xxx, one with the name pcre16_xx, and a third with the name pcre32_xxx.
764    
765  (A) Source files of the PCRE library functions and their headers:  (A) Source files of the PCRE library functions and their headers:
766    
767    dftables.c             auxiliary program for building chartables.c    dftables.c              auxiliary program for building pcre_chartables.c
768                                when --enable-rebuild-chartables is specified
769    
770    pcreposix.c            )    pcre_chartables.c.dist  a default set of character tables that assume ASCII
771    pcre_compile.c         )                              coding; used, unless --enable-rebuild-chartables is
772    pcre_config.c          )                              specified, by copying to pcre[16]_chartables.c
773    pcre_dfa_exec.c        )  
774    pcre_exec.c            )    pcreposix.c                )
775    pcre_fullinfo.c        )    pcre[16|32]_byte_order.c   )
776    pcre_get.c             ) sources for the functions in the library,    pcre[16|32]_compile.c      )
777    pcre_globals.c         )   and some internal functions that they use    pcre[16|32]_config.c       )
778    pcre_info.c            )    pcre[16|32]_dfa_exec.c     )
779    pcre_maketables.c      )    pcre[16|32]_exec.c         )
780    pcre_newline.c         )    pcre[16|32]_fullinfo.c     )
781    pcre_ord2utf8.c        )    pcre[16|32]_get.c          ) sources for the functions in the library,
782    pcre_refcount.c        )    pcre[16|32]_globals.c      )   and some internal functions that they use
783    pcre_study.c           )    pcre[16|32]_jit_compile.c  )
784    pcre_tables.c          )    pcre[16|32]_maketables.c   )
785    pcre_try_flipped.c     )    pcre[16|32]_newline.c      )
786    pcre_ucp_searchfuncs.c )    pcre[16|32]_refcount.c     )
787    pcre_valid_utf8.c      )    pcre[16|32]_string_utils.c )
788    pcre_version.c         )    pcre[16|32]_study.c        )
789    pcre_xclass.c          )    pcre[16|32]_tables.c       )
790    pcre_printint.src      ) debugging function that is #included in pcretest,    pcre[16|32]_ucd.c          )
791                           )   and can also be #included in pcre_compile()    pcre[16|32]_version.c      )
792    pcre.h.in              template for pcre.h when built by "configure"    pcre[16|32]_xclass.c       )
793    pcreposix.h            header for the external POSIX wrapper API    pcre_ord2utf8.c            )
794    pcre_internal.h        header for internal use    pcre_valid_utf8.c          )
795    ucp.h                  ) headers concerned with    pcre16_ord2utf16.c         )
796    ucpinternal.h          )   Unicode property handling    pcre16_utf16_utils.c       )
797    ucptable.h             ) (this one is the data table)    pcre16_valid_utf16.c       )
798      pcre32_utf32_utils.c       )
799    config.h.in            template for config.h, which is built by "configure"    pcre32_valid_utf32.c       )
800    
801    pcrecpp.h              public header file for the C++ wrapper    pcre[16|32]_printint.c     ) debugging function that is used by pcretest,
802    pcrecpparg.h.in        template for another C++ header file                               )   and can also be #included in pcre_compile()
803    pcre_scanner.h         public header file for C++ scanner functions  
804    pcrecpp.cc             )    pcre.h.in               template for pcre.h when built by "configure"
805    pcre_scanner.cc        ) source for the C++ wrapper library    pcreposix.h             header for the external POSIX wrapper API
806      pcre_internal.h         header for internal use
807    pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the    sljit/*                 16 files that make up the JIT compiler
808                             C++ stringpiece functions    ucp.h                   header for Unicode property handling
809    pcre_stringpiece.cc    source for the C++ stringpiece functions  
810      config.h.in             template for config.h, which is built by "configure"
811    
812      pcrecpp.h               public header file for the C++ wrapper
813      pcrecpparg.h.in         template for another C++ header file
814      pcre_scanner.h          public header file for C++ scanner functions
815      pcrecpp.cc              )
816      pcre_scanner.cc         ) source for the C++ wrapper library
817    
818      pcre_stringpiece.h.in   template for pcre_stringpiece.h, the header for the
819                                C++ stringpiece functions
820      pcre_stringpiece.cc     source for the C++ stringpiece functions
821    
822  (B) Source files for programs that use PCRE:  (B) Source files for programs that use PCRE:
823    
824    pcredemo.c             simple demonstration of coding calls to PCRE    pcredemo.c              simple demonstration of coding calls to PCRE
825    pcregrep.c             source of a grep utility that uses PCRE    pcregrep.c              source of a grep utility that uses PCRE
826    pcretest.c             comprehensive test program    pcretest.c              comprehensive test program
827    
828  (C) Auxiliary files:  (C) Auxiliary files:
829    
830    132html                script to turn "man" pages into HTML    132html                 script to turn "man" pages into HTML
831    AUTHORS                information about the author of PCRE    AUTHORS                 information about the author of PCRE
832    ChangeLog              log of changes to the code    ChangeLog               log of changes to the code
833    CleanTxt               script to clean nroff output for txt man pages    CleanTxt                script to clean nroff output for txt man pages
834    Detrail                script to remove trailing spaces    Detrail                 script to remove trailing spaces
835    Index.html             the base HTML page    HACKING                 some notes about the internals of PCRE
836    INSTALL                generic installation instructions    INSTALL                 generic installation instructions
837    LICENCE                conditions for the use of PCRE    LICENCE                 conditions for the use of PCRE
838    COPYING                the same, using GNU's standard name    COPYING                 the same, using GNU's standard name
839    Makefile.in            ) template for Unix Makefile, which is built by    Makefile.in             ) template for Unix Makefile, which is built by
840                           )   "configure"                            )   "configure"
841    Makefile.am            ) the automake input that was used to create    Makefile.am             ) the automake input that was used to create
842                           )   Makefile.in                            )   Makefile.in
843    NEWS                   important changes in this release    NEWS                    important changes in this release
844    NON-UNIX-USE           notes on building PCRE on non-Unix systems    NON-UNIX-USE            the previous name for NON-AUTOTOOLS-BUILD
845    PrepareRelease         script to make preparations for "make dist"    NON-AUTOTOOLS-BUILD     notes on building PCRE without using autotools
846    README                 this file    PrepareRelease          script to make preparations for "make dist"
847    RunTest.in             template for a Unix shell script for running tests    README                  this file
848    RunGrepTest.in         template for a Unix shell script for pcregrep tests    RunTest                 a Unix shell script for running tests
849    aclocal.m4             m4 macros (generated by "aclocal")    RunGrepTest             a Unix shell script for pcregrep tests
850    config.guess           ) files used by libtool,    aclocal.m4              m4 macros (generated by "aclocal")
851    config.sub             )   used only when building a shared library    config.guess            ) files used by libtool,
852    configure              a configuring shell script (built by autoconf)    config.sub              )   used only when building a shared library
853    configure.ac           ) the autoconf input that was used to build    configure               a configuring shell script (built by autoconf)
854                           )   "configure" and config.h    configure.ac            ) the autoconf input that was used to build
855    depcomp                ) script to find program dependencies, generated by                            )   "configure" and config.h
856                           )   automake    depcomp                 ) script to find program dependencies, generated by
857    doc/*.3                man page sources for the PCRE functions                            )   automake
858    doc/*.1                man page sources for pcregrep and pcretest    doc/*.3                 man page sources for PCRE
859    doc/html/*             HTML documentation    doc/*.1                 man page sources for pcregrep and pcretest
860    doc/pcre.txt           plain text version of the man pages    doc/index.html.src      the base HTML page
861    doc/pcretest.txt       plain text documentation of test program    doc/html/*              HTML documentation
862    doc/perltest.txt       plain text documentation of Perl test program    doc/pcre.txt            plain text version of the man pages
863    install-sh             a shell script for installing files    doc/pcretest.txt        plain text documentation of test program
864    libpcre.pc.in          template for libpcre.pc for pkg-config    doc/perltest.txt        plain text documentation of Perl test program
865    libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config    install-sh              a shell script for installing files
866    ltmain.sh              file used to build a libtool script    libpcre16.pc.in         template for libpcre16.pc for pkg-config
867    missing                ) common stub for a few missing GNU programs while    libpcre32.pc.in         template for libpcre32.pc for pkg-config
868                           )   installing, generated by automake    libpcre.pc.in           template for libpcre.pc for pkg-config
869    mkinstalldirs          script for making install directories    libpcreposix.pc.in      template for libpcreposix.pc for pkg-config
870    perltest.pl            Perl test program    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
871    pcre-config.in         source of script which retains PCRE information    ltmain.sh               file used to build a libtool script
872      missing                 ) common stub for a few missing GNU programs while
873                              )   installing, generated by automake
874      mkinstalldirs           script for making install directories
875      perltest.pl             Perl test program
876      pcre-config.in          source of script which retains PCRE information
877      pcre_jit_test.c         test program for the JIT compiler
878    pcrecpp_unittest.cc          )    pcrecpp_unittest.cc          )
879    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
880    pcre_stringpiece_unittest.cc )    pcre_stringpiece_unittest.cc )
881    testdata/testinput*    test data for main library tests    testdata/testinput*     test data for main library tests
882    testdata/testoutput*   expected test results    testdata/testoutput*    expected test results
883    testdata/grep*         input and output for pcregrep tests    testdata/grep*          input and output for pcregrep tests
884      testdata/*              other supporting test files
885    
886  (D) Auxiliary files for cmake support  (D) Auxiliary files for cmake support
887    
888      cmake/COPYING-CMAKE-SCRIPTS
889      cmake/FindPackageHandleStandardArgs.cmake
890      cmake/FindEditline.cmake
891      cmake/FindReadline.cmake
892    CMakeLists.txt    CMakeLists.txt
893    config-cmake.h.in    config-cmake.h.in
894    
895  (E) Auxiliary files for VPASCAL  (E) Auxiliary files for VPASCAL
896    
897    makevp.bat    makevp.bat
898    !compile.txt    makevp_c.txt
899    !linklib.txt    makevp_l.txt
900    pcregexp.pas    pcregexp.pas
901    
902  (F) Auxiliary files for building PCRE "by hand"  (F) Auxiliary files for building PCRE "by hand"
903    
904    pcre.h.generic         ) a version of the public PCRE header file    pcre.h.generic          ) a version of the public PCRE header file
905                           )   for use in non-"configure" environments                            )   for use in non-"configure" environments
906    config.h.generic       ) a version of config.h for use in non-"configure"    config.h.generic        ) a version of config.h for use in non-"configure"
907                           )   environments                            )   environments
908    
909  (F) Miscellaneous  (F) Miscellaneous
910    
# Line 652  The distribution should contain the foll Line 913  The distribution should contain the foll
913  Philip Hazel  Philip Hazel
914  Email local part: ph10  Email local part: ph10
915  Email domain: cam.ac.uk  Email domain: cam.ac.uk
916  Last updated: March 2007  Last updated: 07 September 2012

Legend:
Removed from v.123  
changed lines
  Added in v.1055

  ViewVC Help
Powered by ViewVC 1.1.5