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

Diff of /code/trunk/README

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

revision 251 by ph10, Mon Sep 17 10:33:48 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  There is a mailing list for discussion about the development of PCRE at
12    
# Line 21  The contents of this README file are: Line 24  The contents of this README file are:
24    Shared libraries on Unix-like systems    Shared libraries on Unix-like systems
25    Cross-compiling on Unix-like systems    Cross-compiling on Unix-like systems
26    Using HP's ANSI C++ compiler (aCC)    Using HP's ANSI C++ compiler (aCC)
27      Using PCRE from MySQL
28    Making new tarballs    Making new tarballs
29    Testing PCRE    Testing PCRE
30    Character tables    Character tables
# Line 82  documentation is supplied in two other f Line 86  documentation is supplied in two other f
86       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
87       doc/html and installed in <prefix>/share/doc/pcre/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
95  ------------------------------  ------------------------------
# Line 103  Building PCRE on non-Unix systems Line 111  Building PCRE on non-Unix systems
111    
112  For a non-Unix system, please read the comments in the file NON-UNIX-USE,  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  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.  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  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  straightforward to build PCRE on any system that has a Standard C compiler and
# Line 117  If you are using HP's ANSI C++ compiler Line 127  If you are using HP's ANSI C++ compiler
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,  The following instructions assume the use of the widely used "configure, make,
130  make install" process. There is also some experimental support for "cmake" in  make install" process. There is also support for CMake in the PCRE
131  the PCRE distribution, but it is incomplete and not documented. However, if you  distribution; there are some comments about using CMake in the NON-UNIX-USE
132  are a "cmake" user, you might want to try it.  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
# Line 149  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    it will try to find a C++ compiler and C++ header files, and if it succeeds,    it will try to find a C++ compiler and C++ header files, and if it succeeds,
175    it 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 183  library. You can read more about them in Line 208  library. You can read more about them in
208    to be some failures. With --enable-newline-is-anycrlf or    to be some failures. With --enable-newline-is-anycrlf or
209    --enable-newline-is-any, many tests should succeed, but there may be some    --enable-newline-is-any, many tests should succeed, but there may be some
210    failures.    failures.
211    
212  . By default, the sequence \R in a pattern matches any Unicode line ending  . 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    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    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    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").    --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
# Line 234  library. You can read more about them in Line 259  library. You can read more about them in
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. There is a discussion about stack sizes in the    successfully used, it is not relevant. Equally, it does not apply to
264    pcrestack man page.    pcre_dfa_exec(), which does not use deeply nested recursion. There is a
265      discussion about stack sizes in the pcrestack man page.
266    
267  . For speed, PCRE uses four tables for manipulating and identifying characters  . For speed, PCRE uses four tables for manipulating and identifying characters
268    whose code point values are less than 256. By default, it uses a set of    whose code point values are less than 256. By default, it uses a set of
# Line 250  library. You can read more about them in Line 276  library. You can read more about them in
276    pcre_chartables.c.dist. See "Character tables" below for further information.    pcre_chartables.c.dist. See "Character tables" below for further information.
277    
278  . It is possible to compile PCRE for use on systems that use EBCDIC as their  . It is possible to compile PCRE for use on systems that use EBCDIC as their
279    default character code (as opposed to ASCII) by specifying    character code (as opposed to ASCII) by specifying
280    
281    --enable-ebcdic    --enable-ebcdic
282    
283    This automatically implies --enable-rebuild-chartables (see above).    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:  The "configure" script builds the following files for the basic C library:
324    
325  . Makefile is the makefile that builds the library  . Makefile             the makefile that builds the library
326  . config.h contains build-time configuration options for the library  . config.h             build-time configuration options for the library
327  . pcre.h is the public PCRE header file  . pcre.h               the public PCRE header file
328  . pcre-config is a script that shows the settings of "configure" options  . pcre-config          script that shows the building settings such as CFLAGS
329  . libpcre.pc is data for the pkg-config command                           that were set for "configure"
330  . libtool is a script that builds shared and/or static libraries  . libpcre.pc         ) data for the pkg-config command
331  . RunTest is a script for running tests on the basic C library  . libpcreposix.pc    )
332  . RunGrepTest is a script for running tests on the pcregrep command  . libtool              script that builds shared and/or static libraries
333    . RunTest              script for running tests on the basic C library
334  Versions of config.h and pcre.h are distributed in the PCRE tarballs under  . RunGrepTest          script for running tests on the pcregrep command
335  the names config.h.generic and pcre.h.generic. These are provided for the  
336  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
337  you use "configure", the .generic versions are not used.  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:  If a C++ compiler is found, the following files are also built:
342    
343  . libpcrecpp.pc is data for the pkg-config command  . libpcrecpp.pc        data for the pkg-config command
344  . pcrecpparg.h is a header file for programs that call PCRE via the C++ wrapper  . pcrecpparg.h         header file for calling PCRE via the C++ wrapper
345  . pcre_stringpiece.h is the header for the C++ "stringpiece" functions  . 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
349  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
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, a demonstration  libpcre and libpcreposix, a test program called pcretest, and the pcregrep
353  program called pcredemo, and the pcregrep command. If a C++ compiler was found  command. If a C++ compiler was found on your system, and you did not disable it
354  on your system, "make" also builds the C++ wrapper library, which is called  with --disable-cpp, "make" also builds the C++ wrapper library, which is called
355  libpcrecpp, and some test programs called pcrecpp_unittest,  libpcrecpp, and some test programs called pcrecpp_unittest,
356  pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper  pcre_scanner_unittest, and pcre_stringpiece_unittest. If you enabled JIT
357  can be disabled by adding --disable-cpp to the "configure" command.  support with --enable-jit, a test program called pcre_jit_test is also built.
358    
359  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
360  tests are given below in a separate section of this document.  tests are given below in a separate section of this document.
# Line 309  system. The following are installed (fil Line 375  system. The following are installed (fil
375    
376    Configuration information (lib/pkgconfig):    Configuration information (lib/pkgconfig):
377      libpcre.pc      libpcre.pc
378        libpcreposix.pc
379      libpcrecpp.pc (if C++ support is enabled)      libpcrecpp.pc (if C++ support is enabled)
380    
381    Header files (include):    Header files (include):
# Line 322  system. The following are installed (fil Line 389  system. The following are installed (fil
389    Man pages (share/man/man{1,3}):    Man pages (share/man/man{1,3}):
390      pcregrep.1      pcregrep.1
391      pcretest.1      pcretest.1
392        pcre-config.1
393      pcre.3      pcre.3
394      pcre*.3 (lots more pages, all starting "pcre")      pcre*.3 (lots more pages, all starting "pcre")
395    
# Line 336  system. The following are installed (fil Line 404  system. The following are installed (fil
404      LICENCE      LICENCE
405      NEWS      NEWS
406      README      README
407      pcre.txt       (a concatenation of the man(3) pages)      pcre.txt         (a concatenation of the man(3) pages)
408      pcretest.txt   the pcretest man page      pcretest.txt     the pcretest man page
409      pcregrep.txt   the pcregrep man page      pcregrep.txt     the pcregrep man page
410        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.  
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 438  running the "configure" script: Line 504  running the "configure" script:
504    CXXLDFLAGS="-lstd_v2 -lCsup_v2"    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
505    
506    
507    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  Making new tarballs
528  -------------------  -------------------
529    
# Line 457  To test the basic PCRE library on a Unix Line 543  To test the basic PCRE library on a Unix
543  created by the configuring process. There is also a script called RunGrepTest  created by the configuring process. There is also a script called RunGrepTest
544  that tests the options of the pcregrep command. If the C++ wrapper library is  that tests the options of the pcregrep command. If the C++ wrapper library is
545  built, three 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 also built.  pcre_stringpiece_unittest are also built. When JIT support is enabled, another
547    test program called pcre_jit_test is built.
548    
549  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
550  "make test". For other systems, see the instructions in 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.pl script to  The first test file can be fed directly into the perltest.pl script to check
572  check that Perl gives the same results. The only difference you should see is  that Perl gives the same results. The only difference you should see is in the
573  in the first few lines, where the Perl version is given instead of the PCRE  first few lines, where the Perl version is given instead of the PCRE version.
 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
# Line 506  in the comparison output, it means that Line 602  in the comparison output, it means that
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  [If you are trying to run this test on Windows, you may be able to get it to  [If you are trying to run this test on Windows, you may be able to get it to
605  work by changing "fr_FR" to "french" everywhere it occurs.]  work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
606    RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
607    Windows versions of test 2. More info on using RunTest.bat is included in the
608    document entitled NON-UNIX-USE.]
609    
610  The fourth test checks the UTF-8 support. It is not run automatically unless  The fourth test checks the UTF-8 support. This file can be also fed directly to
611  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when  the perltest.pl script, provided you are running Perl 5.8 or higher.
 running "configure". This file can be also fed directly to the perltest script,  
 provided you are running Perl 5.8 or higher. (For Perl 5.6, a small patch,  
 commented in the script, can be be used.)  
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 test checks the support for Unicode character properties. It it not  The sixth test (which is Perl-5.10 compatible) checks the support for Unicode
617  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
# Line 604  The distribution should contain the foll Line 716  The distribution should contain the foll
716    pcre_get.c              ) sources for the functions in the library,    pcre_get.c              ) sources for the functions in the library,
717    pcre_globals.c          )   and some internal functions that they use    pcre_globals.c          )   and some internal functions that they use
718    pcre_info.c             )    pcre_info.c             )
719      pcre_jit_compile.c      )
720    pcre_maketables.c       )    pcre_maketables.c       )
721    pcre_newline.c          )    pcre_newline.c          )
722    pcre_ord2utf8.c         )    pcre_ord2utf8.c         )
# Line 611  The distribution should contain the foll Line 724  The distribution should contain the foll
724    pcre_study.c            )    pcre_study.c            )
725    pcre_tables.c           )    pcre_tables.c           )
726    pcre_try_flipped.c      )    pcre_try_flipped.c      )
727    pcre_ucp_searchfuncs.c  )    pcre_ucd.c              )
728    pcre_valid_utf8.c       )    pcre_valid_utf8.c       )
729    pcre_version.c          )    pcre_version.c          )
730    pcre_xclass.c           )    pcre_xclass.c           )
# Line 620  The distribution should contain the foll Line 733  The distribution should contain the foll
733    pcre.h.in               template for pcre.h when built by "configure"    pcre.h.in               template for pcre.h when built by "configure"
734    pcreposix.h             header for the external POSIX wrapper API    pcreposix.h             header for the external POSIX wrapper API
735    pcre_internal.h         header for internal use    pcre_internal.h         header for internal use
736    ucp.h                   ) headers concerned with    sljit/*                 16 files that make up the JIT compiler
737    ucpinternal.h           )   Unicode property handling    ucp.h                   header for Unicode property handling
   ucptable.h              ) (this one is the data table)  
738    
739    config.h.in             template for config.h, which is built by "configure"    config.h.in             template for config.h, which is built by "configure"
740    
# Line 671  The distribution should contain the foll Line 783  The distribution should contain the foll
783                            )   "configure" and config.h                            )   "configure" and config.h
784    depcomp                 ) script to find program dependencies, generated by    depcomp                 ) script to find program dependencies, generated by
785                            )   automake                            )   automake
786    doc/*.3                 man page sources for the PCRE functions    doc/*.3                 man page sources for PCRE
787    doc/*.1                 man page sources for pcregrep and pcretest    doc/*.1                 man page sources for pcregrep and pcretest
788    doc/index.html.src      the base HTML page    doc/index.html.src      the base HTML page
789    doc/html/*              HTML documentation    doc/html/*              HTML documentation
# Line 680  The distribution should contain the foll Line 792  The distribution should contain the foll
792    doc/perltest.txt        plain text documentation of Perl test program    doc/perltest.txt        plain text documentation of Perl test program
793    install-sh              a shell script for installing files    install-sh              a shell script for installing files
794    libpcre.pc.in           template for libpcre.pc for pkg-config    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    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
797    ltmain.sh               file used to build a libtool script    ltmain.sh               file used to build a libtool script
798    missing                 ) common stub for a few missing GNU programs while    missing                 ) common stub for a few missing GNU programs while
# Line 687  The distribution should contain the foll Line 800  The distribution should contain the foll
800    mkinstalldirs           script for making install directories    mkinstalldirs           script for making install directories
801    perltest.pl             Perl test program    perltest.pl             Perl test program
802    pcre-config.in          source of script which retains PCRE information    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          )    pcrecpp_unittest.cc          )
805    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
806    pcre_stringpiece_unittest.cc )    pcre_stringpiece_unittest.cc )
# Line 696  The distribution should contain the foll Line 810  The distribution should contain the foll
810    
811  (D) Auxiliary files for cmake support  (D) Auxiliary files for cmake support
812    
813      cmake/COPYING-CMAKE-SCRIPTS
814      cmake/FindPackageHandleStandardArgs.cmake
815      cmake/FindReadline.cmake
816    CMakeLists.txt    CMakeLists.txt
817    config-cmake.h.in    config-cmake.h.in
818    
# Line 720  The distribution should contain the foll Line 837  The distribution should contain the foll
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  Last updated: 17 September 2007  Last updated: 23 August 2011

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

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12