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

Diff of /code/trunk/README

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

revision 873 by ph10, Sat Jan 14 16:45:24 2012 UTC revision 1178 by ph10, Sat Oct 27 16:49:31 2012 UTC
# Line 18  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    Using PCRE from MySQL
29    Making new tarballs    Making new tarballs
# Line 34  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. There are two sets of functions,  PCRE is written in C, and it has its own API. There are three sets of functions,
39  one for the 8-bit library, which processes strings of bytes, and one for the  one for the 8-bit library, which processes strings of bytes, one for the
40  16-bit library, which processes strings of 16-bit values. The distribution also  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  includes a set of C++ wrapper functions (see the pcrecpp man page for details),  includes a set of C++ wrapper functions (see the pcrecpp man page for details),
43  courtesy of Google Inc., which can be used to call the 8-bit PCRE library from  courtesy of Google Inc., which can be used to call the 8-bit PCRE library from
44  C++.  C++.
# Line 109  Windows (I myself do not use Windows). N Line 111  Windows (I myself do not use Windows). N
111  in the standard distribution, so these contibutions have been archived.  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. PCRE can also be  "make" you may be able to build PCRE using autotools in the same way as for
120  configured in many platform environments using the GUI facility provided by  many Unix-like systems.
121  CMake's cmake-gui command. This creates Makefiles, solution files, etc.  
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  The following instructions assume the use of the widely used "configure, make,  The following instructions assume the use of the widely used "configure; make;
146  make install" process. There is also support for CMake in the PCRE  make install" (autotools) process.
147  distribution; there are some comments about using CMake in the NON-UNIX-USE  
148  file, though it can also be used in Unix-like systems.  To build PCRE on system that supports autotools, first run the "configure"
149    command from the PCRE distribution directory, with your current directory set
150  To build PCRE on a Unix-like system, first run the "configure" command from the  to the directory where you want the files to be created. This command is a
151  PCRE distribution directory, with your current directory set to the directory  standard GNU "autoconf" configuration script, for which generic instructions
152  where you want the files to be created. This command is a standard GNU  are supplied in the file INSTALL.
 "autoconf" configuration script, for which generic instructions 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 173  library. They are also documented in the Line 184  library. They are also documented in the
184    (See also "Shared libraries on Unix-like systems" below.)    (See also "Shared libraries on Unix-like systems" below.)
185    
186  . By default, only the 8-bit library is built. If you add --enable-pcre16 to  . By default, only the 8-bit library is built. If you add --enable-pcre16 to
187    the "configure" command, the 16-bit library is also built. If you want only    the "configure" command, the 16-bit library is also built. If you add
188    the 16-bit library, use "./configure --enable-pcre16 --disable-pcre8".    --enable-pcre32 to the "configure" command, the 32-bit library is also built.
189      If you want only the 16-bit or 32-bit library, use --disable-pcre8 to disable
190      building the 8-bit library.
191    
192  . If you are building the 8-bit library and want to suppress the building of  . If you are building the 8-bit library and want to suppress the building of
193    the C++ wrapper library, you can add --disable-cpp to the "configure"    the C++ wrapper library, you can add --disable-cpp to the "configure"
# Line 193  library. They are also documented in the Line 206  library. They are also documented in the
206    
207  . If you want to make use of the support for UTF-8 Unicode character strings in  . 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,    the 8-bit library, or UTF-16 Unicode character strings in the 16-bit library,
209    you must add --enable-utf to the "configure" command. Without it, the code    or UTF-32 Unicode character strings in the 32-bit library, you must add
210    for handling UTF-8 and UTF-16 is not included in the relevant library. Even    --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    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    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, even when running on EBCDIC    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    platforms. It is not possible to use both --enable-utf and --enable-ebcdic at
216    the same time.    the same time.
217    
218  . There are no separate options for enabling UTF-8 and UTF-16 independently  . There are no separate options for enabling UTF-8, UTF-16 and UTF-32
219    because that would allow ridiculous settings such as requesting UTF-16    independently because that would allow ridiculous settings such as requesting
220    support while building only the 8-bit library. However, the option    UTF-16 support while building only the 8-bit library. However, the option
221    --enable-utf8 is retained for backwards compatibility with earlier releases    --enable-utf8 is retained for backwards compatibility with earlier releases
222    that did not support 16-bit character strings. It is synonymous with    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    --enable-utf. It is not possible to configure one library with UTF support
224    and the other without in the same configuration.    and the other without in the same configuration.
225    
226  . If, in addition to support for UTF-8/16 character strings, you want to  . 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    include support for the \P, \p, and \X sequences that recognize Unicode
228    character properties, you must add --enable-unicode-properties to the    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    "configure" command. This adds about 30K to the size of the library (in the
# Line 271  library. They are also documented in the Line 285  library. They are also documented in the
285    library, PCRE then uses three bytes instead of two for offsets to different    library, PCRE then uses three bytes instead of two for offsets to different
286    parts of the compiled pattern. In the 16-bit library, --with-link-size=3 is    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    the same as --with-link-size=4, which (in both libraries) uses four-byte
288    offsets. Increasing the internal link size reduces performance.    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 300  library. They are also documented in the Line 315  library. They are also documented in the
315    pcre_chartables.c.dist. See "Character tables" below for further information.    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  . It is possible to compile PCRE for use on systems that use EBCDIC as their
318    character code (as opposed to ASCII) by specifying    character code (as opposed to ASCII/Unicode) by specifying
319    
320    --enable-ebcdic    --enable-ebcdic
321    
322    This automatically implies --enable-rebuild-chartables (see above). However,    This automatically implies --enable-rebuild-chartables (see above). However,
323    when PCRE is built this way, it always operates in EBCDIC. It cannot support    when PCRE is built this way, it always operates in EBCDIC. It cannot support
324    both EBCDIC and UTF-8/16.    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    . In environments where valgrind is installed, if you specify
329    
330      --enable-valgrind
331    
332      PCRE will use valgrind annotations to mark certain memory regions as
333      unaddressable. This allows it to detect invalid memory accesses, and is
334      mostly useful for debugging PCRE itself.
335    
336    . In environments where the gcc compiler is used and lcov version 1.6 or above
337      is installed, if you specify
338    
339      --enable-coverage
340    
341      the build process implements a code coverage report for the test suite. The
342      report is generated by running "make coverage". If ccache is installed on
343      your system, it must be disabled when building PCRE for coverage reporting.
344      You can do this by setting the environment variable CCACHE_DISABLE=1 before
345      running "make" to build PCRE.
346    
347  . The pcregrep program currently supports only 8-bit data files, and so  . The pcregrep program currently supports only 8-bit data files, and so
348    requires the 8-bit PCRE library. It is possible to compile pcregrep to use    requires the 8-bit PCRE library. It is possible to compile pcregrep to use
349    libz and/or libbz2, in order to read .gz and .bz2 files (respectively), by    libz and/or libbz2, in order to read .gz and .bz2 files (respectively), by
# Line 326  library. They are also documented in the Line 362  library. They are also documented in the
362    The default value is 20K.    The default value is 20K.
363    
364  . It is possible to compile pcretest so that it links with the libreadline  . It is possible to compile pcretest so that it links with the libreadline
365    library, by specifying    or libedit libraries, by specifying, respectively,
366    
367    --enable-pcretest-libreadline    --enable-pcretest-libreadline or --enable-pcretest-libedit
368    
369    If this is done, when pcretest's input is from a terminal, it reads it using    If this is done, when pcretest's input is from a terminal, it reads it using
370    the readline() function. This provides line-editing and history facilities.    the readline() function. This provides line-editing and history facilities.
371    Note that libreadline is GPL-licenced, so if you distribute a binary of    Note that libreadline is GPL-licenced, so if you distribute a binary of
372    pcretest linked in this way, there may be licensing issues.    pcretest linked in this way, there may be licensing issues. These can be
373      avoided by linking with libedit (which has a BSD licence) instead.
374    
375    Setting this option causes the -lreadline option to be added to the pcretest    Enabling libreadline causes the -lreadline option to be added to the pcretest
376    build. In many operating environments with a sytem-installed readline    build. In many operating environments with a sytem-installed readline
377    library this is sufficient. However, in some environments (e.g. if an    library this is sufficient. However, in some environments (e.g. if an
378    unmodified distribution version of readline is in use), it may be necessary    unmodified distribution version of readline is in use), it may be necessary
# Line 355  The "configure" script builds the follow Line 392  The "configure" script builds the follow
392                           that were set for "configure"                           that were set for "configure"
393  . libpcre.pc         ) data for the pkg-config command  . libpcre.pc         ) data for the pkg-config command
394  . libpcre16.pc       )  . libpcre16.pc       )
395    . libpcre32.pc       )
396  . libpcreposix.pc    )  . libpcreposix.pc    )
397  . libtool              script that builds shared and/or static libraries  . libtool              script that builds shared and/or static libraries
 . RunTest              script for running tests on the basic C library  
 . RunGrepTest          script for running tests on the pcregrep command  
398    
399  Versions of config.h and pcre.h are distributed in the PCRE tarballs under the  Versions of config.h and pcre.h are distributed in the PCRE tarballs under the
400  names config.h.generic and pcre.h.generic. These are provided for those who  names config.h.generic and pcre.h.generic. These are provided for those who
# Line 376  The "configure" script also creates conf Line 412  The "configure" script also creates conf
412  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
413  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
414    
415  Once "configure" has run, you can run "make". This builds either or both of the  Once "configure" has run, you can run "make". This builds the the libraries
416  libraries libpcre and libpcre16, and a test program called pcretest. If you  libpcre, libpcre16 and/or libpcre32, and a test program called pcretest. If you
417  enabled JIT support with --enable-jit, a test program called pcre_jit_test is  enabled JIT support with --enable-jit, a test program called pcre_jit_test is
418  built as well.  built as well.
419    
# Line 401  system. The following are installed (fil Line 437  system. The following are installed (fil
437    
438    Libraries (lib):    Libraries (lib):
439      libpcre16     (if 16-bit support is enabled)      libpcre16     (if 16-bit support is enabled)
440        libpcre32     (if 32-bit support is enabled)
441      libpcre       (if 8-bit support is enabled)      libpcre       (if 8-bit support is enabled)
442      libpcreposix  (if 8-bit support is enabled)      libpcreposix  (if 8-bit support is enabled)
443      libpcrecpp    (if 8-bit and C++ support is enabled)      libpcrecpp    (if 8-bit and C++ support is enabled)
444    
445    Configuration information (lib/pkgconfig):    Configuration information (lib/pkgconfig):
446      libpcre16.pc      libpcre16.pc
447        libpcre32.pc
448      libpcre.pc      libpcre.pc
449      libpcreposix.pc      libpcreposix.pc
450      libpcrecpp.pc (if C++ support is enabled)      libpcrecpp.pc (if C++ support is enabled)
# Line 447  This removes all the files that "make in Line 485  This removes all the files that "make in
485  remove any directories, because these are often shared with other programs.  remove any directories, because these are often shared with other programs.
486    
487    
488  Retrieving configuration information on Unix-like systems  Retrieving configuration information
489  ---------------------------------------------------------  ------------------------------------
490    
491  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
492  recall information about the PCRE configuration and installation. For example:  recall information about the PCRE configuration and installation. For example:
# Line 473  The data is held in *.pc files that are Line 511  The data is held in *.pc files that are
511  <prefix>/lib/pkgconfig.  <prefix>/lib/pkgconfig.
512    
513    
514  Shared libraries on Unix-like systems  Shared libraries
515  -------------------------------------  ----------------
516    
517  The default distribution builds PCRE as shared libraries and static libraries,  The default distribution builds PCRE as shared libraries and static libraries,
518  as long as the operating system supports shared libraries. Shared library  as long as the operating system supports shared libraries. Shared library
# Line 499  Then run "make" in the usual way. Simila Line 537  Then run "make" in the usual way. Simila
537  build only shared libraries.  build only shared libraries.
538    
539    
540  Cross-compiling on Unix-like systems  Cross-compiling using autotools
541  ------------------------------------  -------------------------------
542    
543  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
544  order to cross-compile PCRE for some other host. However, you should NOT  order to cross-compile PCRE for some other host. However, you should NOT
# Line 572  script creates the .txt and HTML forms o Line 610  script creates the .txt and HTML forms o
610  Testing PCRE  Testing PCRE
611  ------------  ------------
612    
613  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.
614  created by the configuring process. There is also a script called RunGrepTest  There is another script called RunGrepTest that tests the options of the
615  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
616  built, three test programs called pcrecpp_unittest, pcre_scanner_unittest, and  called pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest
617  pcre_stringpiece_unittest are also built. When JIT support is enabled, another  are also built. When JIT support is enabled, another test program called
618  test program called pcre_jit_test is built.  pcre_jit_test is built.
619    
620  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
621  "make test". For other systems, see the instructions in NON-UNIX-USE.  "make test". For other environments, see the instructions in
622    NON-AUTOTOOLS-BUILD.
623    
624  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
625  own man page) on each of the relevant testinput files in the testdata  own man page) on each of the relevant testinput files in the testdata
626  directory, and compares the output with the contents of the corresponding  directory, and compares the output with the contents of the corresponding
627  testoutput files. Some tests are relevant only when certain build-time options  testoutput files. Some tests are relevant only when certain build-time options
628  were selected. For example, the tests for UTF-8/16 support are run only if  were selected. For example, the tests for UTF-8/16/32 support are run only if
629  --enable-utf was used. RunTest outputs a comment when it skips a test.  --enable-utf was used. RunTest outputs a comment when it skips a test.
630    
631  Many of the tests that are not skipped are run up to three times. The second  Many of the tests that are not skipped are run up to three times. The second
# Line 595  tests that are marked "never study" (see Line 634  tests that are marked "never study" (see
634  done). If JIT support is available, the non-DFA tests are run a third time,  done). If JIT support is available, the non-DFA tests are run a third time,
635  this time with a forced pcre_study() with the PCRE_STUDY_JIT_COMPILE option.  this time with a forced pcre_study() with the PCRE_STUDY_JIT_COMPILE option.
636    
637  When both 8-bit and 16-bit support is enabled, the entire set of tests is run  The entire set of tests is run once for each of the 8-bit, 16-bit and 32-bit
638  twice, once for each library. If you want to run just one set of tests, call  libraries that are enabled. If you want to run just one set of tests, call
639  RunTest with either the -8 or -16 option.  RunTest with either the -8, -16 or -32 option.
640    
641  RunTest uses a file called testtry to hold the main output from pcretest.  RunTest uses a file called testtry to hold the main output from pcretest.
642  Other files whose names begin with "test" are used as working files in some  Other files whose names begin with "test" are used as working files in some
# Line 606  numbers as arguments to RunTest, for exa Line 645  numbers as arguments to RunTest, for exa
645    
646    RunTest 2 7 11    RunTest 2 7 11
647    
648    You can also call RunTest with the single argument "list" to cause it to output
649    a list of tests.
650    
651  The first test file can be fed directly into the perltest.pl script to check  The first test file can be fed directly into the perltest.pl script to check
652  that Perl gives the same results. The only difference you should see is in the  that Perl gives the same results. The only difference you should see is in the
653  first few lines, where the Perl version is given instead of the PCRE version.  first few lines, where the Perl version is given instead of the PCRE version.
# Line 645  RunTest.bat. The version of RunTest.bat Line 687  RunTest.bat. The version of RunTest.bat
687  Windows versions of test 2. More info on using RunTest.bat is included in the  Windows versions of test 2. More info on using RunTest.bat is included in the
688  document entitled NON-UNIX-USE.]  document entitled NON-UNIX-USE.]
689    
690  The fourth and fifth tests check the UTF-8/16 support and error handling and  The fourth and fifth tests check the UTF-8/16/32 support and error handling and
691  internal UTF features of PCRE that are not relevant to Perl, respectively. The  internal UTF features of PCRE that are not relevant to Perl, respectively. The
692  sixth and seventh tests do the same for Unicode character properties support.  sixth and seventh tests do the same for Unicode character properties support.
693    
694  The eighth, ninth, and tenth tests check the pcre_dfa_exec() alternative  The eighth, ninth, and tenth tests check the pcre_dfa_exec() alternative
695  matching function, in non-UTF-8/16 mode, UTF-8/16 mode, and UTF-8/16 mode with  matching function, in non-UTF-8/16/32 mode, UTF-8/16/32 mode, and UTF-8/16/32
696  Unicode property support, respectively.  mode with Unicode property support, respectively.
697    
698  The eleventh test checks some internal offsets and code size features; it is  The eleventh test checks some internal offsets and code size features; it is
699  run only when the default "link size" of 2 is set (in other cases the sizes  run only when the default "link size" of 2 is set (in other cases the sizes
# Line 662  test is run only when JIT support is not Line 704  test is run only when JIT support is not
704  features such as information output from pcretest about JIT compilation.  features such as information output from pcretest about JIT compilation.
705    
706  The fourteenth, fifteenth, and sixteenth tests are run only in 8-bit mode, and  The fourteenth, fifteenth, and sixteenth tests are run only in 8-bit mode, and
707  the seventeenth, eighteenth, and nineteenth tests are run only in 16-bit mode.  the seventeenth, eighteenth, and nineteenth tests are run only in 16/32-bit mode.
708  These are tests that generate different output in the two modes. They are for  These are tests that generate different output in the two modes. They are for
709  general cases, UTF-8/16 support, and Unicode property support, respectively.  general cases, UTF-8/16/32 support, and Unicode property support, respectively.
710    
711    The twentieth test is run only in 16/32-bit mode. It tests some specific
712    16/32-bit features of the DFA matching engine.
713    
714    The twenty-first and twenty-second tests are run only in 16/32-bit mode, when the
715    link size is set to 2 for the 16-bit library. They test reloading pre-compiled patterns.
716    
717  The twentieth test is run only in 16-bit mode. It tests some specific 16-bit  The twenty-third and twenty-fourth tests are run only in 16-bit mode. They are for
718  features of the DFA matching engine.  general cases, and UTF-16 support, respectively.
719    
720    The twenty-fifth and twenty-sixth tests are run only in 32-bit mode. They are for
721    general cases, and UTF-32 support, respectively.
722    
723  Character tables  Character tables
724  ----------------  ----------------
# Line 728  File manifest Line 778  File manifest
778  -------------  -------------
779    
780  The distribution should contain the files listed below. Where a file name is  The distribution should contain the files listed below. Where a file name is
781  given as pcre[16]_xxx it means that there are two files, one with the name  given as pcre[16|32]_xxx it means that there are three files, one with the name
782  pcre_xxx and the other with the name pcre16_xxx.  pcre_xxx, one with the name pcre16_xx, and a third with the name pcre32_xxx.
783    
784  (A) Source files of the PCRE library functions and their headers:  (A) Source files of the PCRE library functions and their headers:
785    
# Line 740  pcre_xxx and the other with the name pcr Line 790  pcre_xxx and the other with the name pcr
790                              coding; used, unless --enable-rebuild-chartables is                              coding; used, unless --enable-rebuild-chartables is
791                              specified, by copying to pcre[16]_chartables.c                              specified, by copying to pcre[16]_chartables.c
792    
793    pcreposix.c             )    pcreposix.c                )
794    pcre[16]_byte_order.c   )    pcre[16|32]_byte_order.c   )
795    pcre[16]_compile.c      )    pcre[16|32]_compile.c      )
796    pcre[16]_config.c       )    pcre[16|32]_config.c       )
797    pcre[16]_dfa_exec.c     )    pcre[16|32]_dfa_exec.c     )
798    pcre[16]_exec.c         )    pcre[16|32]_exec.c         )
799    pcre[16]_fullinfo.c     )    pcre[16|32]_fullinfo.c     )
800    pcre[16]_get.c          ) sources for the functions in the library,    pcre[16|32]_get.c          ) sources for the functions in the library,
801    pcre[16]_globals.c      )   and some internal functions that they use    pcre[16|32]_globals.c      )   and some internal functions that they use
802    pcre[16]_jit_compile.c  )    pcre[16|32]_jit_compile.c  )
803    pcre[16]_maketables.c   )    pcre[16|32]_maketables.c   )
804    pcre[16]_newline.c      )    pcre[16|32]_newline.c      )
805    pcre[16]_refcount.c     )    pcre[16|32]_refcount.c     )
806    pcre[16]_string_utils.c )    pcre[16|32]_string_utils.c )
807    pcre[16]_study.c        )    pcre[16|32]_study.c        )
808    pcre[16]_tables.c       )    pcre[16|32]_tables.c       )
809    pcre[16]_ucd.c          )    pcre[16|32]_ucd.c          )
810    pcre[16]_version.c      )    pcre[16|32]_version.c      )
811    pcre[16]_xclass.c       )    pcre[16|32]_xclass.c       )
812    pcre_ord2utf8.c         )    pcre_ord2utf8.c            )
813    pcre_valid_utf8.c       )    pcre_valid_utf8.c          )
814    pcre16_ord2utf16.c      )    pcre16_ord2utf16.c         )
815    pcre16_utf16_utils.c    )    pcre16_utf16_utils.c       )
816    pcre16_valid_utf16.c    )    pcre16_valid_utf16.c       )
817      pcre32_utf32_utils.c       )
818      pcre32_valid_utf32.c       )
819    
820    pcre[16]_printint.c     ) debugging function that is used by pcretest,    pcre[16|32]_printint.c     ) debugging function that is used by pcretest,
821                            )   and can also be #included in pcre_compile()                               )   and can also be #included in pcre_compile()
822    
823    pcre.h.in               template for pcre.h when built by "configure"    pcre.h.in               template for pcre.h when built by "configure"
824    pcreposix.h             header for the external POSIX wrapper API    pcreposix.h             header for the external POSIX wrapper API
# Line 808  pcre_xxx and the other with the name pcr Line 860  pcre_xxx and the other with the name pcr
860    Makefile.am             ) the automake input that was used to create    Makefile.am             ) the automake input that was used to create
861                            )   Makefile.in                            )   Makefile.in
862    NEWS                    important changes in this release    NEWS                    important changes in this release
863    NON-UNIX-USE            notes on building PCRE on non-Unix systems    NON-UNIX-USE            the previous name for NON-AUTOTOOLS-BUILD
864      NON-AUTOTOOLS-BUILD     notes on building PCRE without using autotools
865    PrepareRelease          script to make preparations for "make dist"    PrepareRelease          script to make preparations for "make dist"
866    README                  this file    README                  this file
867    RunTest                 a Unix shell script for running tests    RunTest                 a Unix shell script for running tests
# Line 830  pcre_xxx and the other with the name pcr Line 883  pcre_xxx and the other with the name pcr
883    doc/perltest.txt        plain text documentation of Perl test program    doc/perltest.txt        plain text documentation of Perl test program
884    install-sh              a shell script for installing files    install-sh              a shell script for installing files
885    libpcre16.pc.in         template for libpcre16.pc for pkg-config    libpcre16.pc.in         template for libpcre16.pc for pkg-config
886      libpcre32.pc.in         template for libpcre32.pc for pkg-config
887    libpcre.pc.in           template for libpcre.pc for pkg-config    libpcre.pc.in           template for libpcre.pc for pkg-config
888    libpcreposix.pc.in      template for libpcreposix.pc for pkg-config    libpcreposix.pc.in      template for libpcreposix.pc for pkg-config
889    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
# Line 852  pcre_xxx and the other with the name pcr Line 906  pcre_xxx and the other with the name pcr
906    
907    cmake/COPYING-CMAKE-SCRIPTS    cmake/COPYING-CMAKE-SCRIPTS
908    cmake/FindPackageHandleStandardArgs.cmake    cmake/FindPackageHandleStandardArgs.cmake
909      cmake/FindEditline.cmake
910    cmake/FindReadline.cmake    cmake/FindReadline.cmake
911    CMakeLists.txt    CMakeLists.txt
912    config-cmake.h.in    config-cmake.h.in
# Line 877  pcre_xxx and the other with the name pcr Line 932  pcre_xxx and the other with the name pcr
932  Philip Hazel  Philip Hazel
933  Email local part: ph10  Email local part: ph10
934  Email domain: cam.ac.uk  Email domain: cam.ac.uk
935  Last updated: 30 December 2011  Last updated: 27 October 2012

Legend:
Removed from v.873  
changed lines
  Added in v.1178

  ViewVC Help
Powered by ViewVC 1.1.5