/[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 338 by ph10, Sun Apr 13 14:58:34 2008 UTC
# Line 30  The contents of this README file are: Line 30  The contents of this README file are:
30  The PCRE APIs  The PCRE APIs
31  -------------  -------------
32    
33  PCRE is written in C, and it has its own API. The distribution now includes a  PCRE is written in C, and it has its own API. The distribution also includes a
34  set of C++ wrapper functions, courtesy of Google Inc. (see the pcrecpp man page  set of C++ wrapper functions (see the pcrecpp man page for details), courtesy
35  for details).  of Google Inc.
36    
37  Also included in the distribution are a set of C wrapper functions that are  In addition, there is a set of C wrapper functions that are based on the POSIX
38  based on the POSIX API. These end up in the library called libpcreposix. Note  regular expression API (see the pcreposix man page). These end up in the
39  that this just provides a POSIX calling interface to PCRE; the regular  library called libpcreposix. Note that this just provides a POSIX calling
40  expressions themselves still follow Perl syntax and semantics. The POSIX API is  interface to PCRE; the regular expressions themselves still follow Perl syntax
41  restricted, and does not give full access to all of PCRE's facilities.  and semantics. The POSIX API is restricted, and does not give full access to
42    all of PCRE's facilities.
43    
44  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
45  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 91  You can find contributions from PCRE use Line 92  You can find contributions from PCRE use
92    
93  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
94  complete in themselves; others are pointers to URLs containing relevant files.  complete in themselves; others are pointers to URLs containing relevant files.
95  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
96  of the contributions provide support for compiling PCRE on various flavours of  contributions provided support for compiling PCRE on various flavours of
97  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
98  support in the standard distribution.  in the standard distribution, so these contibutions have been archived.
99    
100    
101  Building PCRE on non-Unix systems  Building PCRE on non-Unix systems
# Line 102  Building PCRE on non-Unix systems Line 103  Building PCRE on non-Unix systems
103    
104  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,
105  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
106  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
107    configured in many platform environments using the GUI facility of CMake's
108    CMakeSetup. It creates Makefiles, solution files, etc.
109    
110  PCRE has been compiled on many different operating systems. It should be  PCRE has been compiled on many different operating systems. It should be
111  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 115  Building PCRE on Unix-like systems Line 118  Building PCRE on Unix-like systems
118  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
119  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
120    
121    The following instructions assume the use of the widely used "configure, make,
122    make install" process. There is also support for CMake in the PCRE
123    distribution; there are some comments about using CMake in the NON-UNIX-USE
124    file, though it can also be used in Unix-like systems.
125    
126  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
127  PCRE distribution directory, with your current directory set to the directory  PCRE distribution directory, with your current directory set to the directory
128  where you want the files to be created. This command is a standard GNU  where you want the files to be created. This command is a standard GNU
# Line 147  library. You can read more about them in Line 155  library. You can read more about them in
155    
156  . 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
157    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,    --disable-cpp to the "configure" command. Otherwise, when "configure" is run,
158    will try to find a C++ compiler and C++ header files, and if it succeeds, it    it will try to find a C++ compiler and C++ header files, and if it succeeds,
159    will try to build the C++ wrapper.    it will try to build the C++ wrapper.
160    
161  . If you want to make use of the support for UTF-8 character strings in PCRE,  . If you want to make use of the support for UTF-8 character strings in PCRE,
162    you must add --enable-utf8 to the "configure" command. Without it, the code    you must add --enable-utf8 to the "configure" command. Without it, the code
# Line 163  library. You can read more about them in Line 171  library. You can read more about them in
171    supported.    supported.
172    
173  . 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
174    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
175    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
176    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
177    (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
178    --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
179    to the "configure" command, respectively.    or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
180      --enable-newline-is-any to the "configure" command, respectively.
181    If you specify --newline-is-cr or --newline-is-crlf, some of the standard  
182    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
183    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
184    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
185    some failures.    to be some failures. With --enable-newline-is-anycrlf or
186      --enable-newline-is-any, many tests should succeed, but there may be some
187      failures.
188    
189    . By default, the sequence \R in a pattern matches any Unicode line ending
190      sequence. This is independent of the option specifying what PCRE considers to
191      be the end of a line (see above). However, the caller of PCRE can restrict \R
192      to match only CR, LF, or CRLF. You can make this the default by adding
193      --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
194    
195  . When called via the POSIX interface, PCRE uses malloc() to get additional  . When called via the POSIX interface, PCRE uses malloc() to get additional
196    storage for processing capturing parentheses if there are more than 10 of    storage for processing capturing parentheses if there are more than 10 of
197    them. You can increase this threshold by setting, for example,    them in a pattern. You can increase this threshold by setting, for example,
198    
199    --with-posix-malloc-threshold=20    --with-posix-malloc-threshold=20
200    
# Line 207  library. You can read more about them in Line 223  library. You can read more about them in
223  . The default maximum compiled pattern size is around 64K. You can increase  . The default maximum compiled pattern size is around 64K. You can increase
224    this by adding --with-link-size=3 to the "configure" command. You can    this by adding --with-link-size=3 to the "configure" command. You can
225    increase it even more by setting --with-link-size=4, but this is unlikely    increase it even more by setting --with-link-size=4, but this is unlikely
226    ever to be necessary.    ever to be necessary. Increasing the internal link size will reduce
227      performance.
228    
229  . 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
230    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 223  library. You can read more about them in Line 240  library. You can read more about them in
240    use deeply nested recursion. There is a discussion about stack sizes in the    use deeply nested recursion. There is a discussion about stack sizes in the
241    pcrestack man page.    pcrestack man page.
242    
243    . For speed, PCRE uses four tables for manipulating and identifying characters
244      whose code point values are less than 256. By default, it uses a set of
245      tables for ASCII encoding that is part of the distribution. If you specify
246    
247      --enable-rebuild-chartables
248    
249      a program called dftables is compiled and run in the default C locale when
250      you obey "make". It builds a source file called pcre_chartables.c. If you do
251      not specify this option, pcre_chartables.c is created as a copy of
252      pcre_chartables.c.dist. See "Character tables" below for further information.
253    
254    . It is possible to compile PCRE for use on systems that use EBCDIC as their
255      default character code (as opposed to ASCII) by specifying
256    
257      --enable-ebcdic
258    
259      This automatically implies --enable-rebuild-chartables (see above).
260    
261    . It is possible to compile pcregrep to use libz and/or libbz2, in order to
262      read .gz and .bz2 files (respectively), by specifying one or both of
263    
264      --enable-pcregrep-libz
265      --enable-pcregrep-libbz2
266    
267      Of course, the relevant libraries must be installed on your system.
268    
269    . It is possible to compile pcretest so that it links with the libreadline
270      library, by specifying
271    
272      --enable-pcretest-libreadline
273    
274      If this is done, when pcretest's input is from a terminal, it reads it using
275      the readline() function. This provides line-editing and history facilities.
276      Note that libreadline is GPL-licenced, so if you distribute a binary of
277      pcretest linked in this way, there may be licensing issues.
278    
279      Setting this option causes the -lreadline option to be added to the pcretest
280      build. In many operating environments with a sytem-installed readline
281      library this is sufficient. However, in some environments (e.g. if an
282      unmodified distribution version of readline is in use), it may be necessary
283      to specify something like LIBS="-lncurses" as well. This is because, to quote
284      the readline INSTALL, "Readline uses the termcap functions, but does not link
285      with the termcap or curses library itself, allowing applications which link
286      with readline the to choose an appropriate library."
287    
288  The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
289    
290  . Makefile is the makefile that builds the library  . Makefile is the makefile that builds the library
# Line 250  script that can be run to recreate the c Line 312  script that can be run to recreate the c
312  contains compiler output from tests that "configure" runs.  contains compiler output from tests that "configure" runs.
313    
314  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
315  libpcre and libpcreposix, a test program called pcretest, a demonstration  libpcre and libpcreposix, a test program called pcretest, and the pcregrep
316  program called pcredemo, and the pcregrep command. If a C++ compiler was found  command. If a C++ compiler was found on your system, "make" also builds the C++
317  on your system, "make" also builds the C++ wrapper library, which is called  wrapper library, which is called libpcrecpp, and some test programs called
318  libpcrecpp, and some test programs called pcrecpp_unittest,  pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
319  pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper  Building the C++ wrapper can be disabled by adding --disable-cpp to the
320  can be disabled by adding --disable-cpp to the "configure" command.  "configure" command.
321    
322  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
323  tests are given below in a separate section of this document.  tests are given below in a separate section of this document.
# Line 307  system. The following are installed (fil Line 369  system. The following are installed (fil
369      pcretest.txt   the pcretest man page      pcretest.txt   the pcretest man page
370      pcregrep.txt   the pcregrep man page      pcregrep.txt   the pcregrep man page
371    
 Note that the pcredemo program that is built by "configure" is *not* installed  
 anywhere. It is a demonstration for programmers wanting to use PCRE.  
   
372  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".
373  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
374  remove any directories, because these are often shared with other programs.  remove any directories, because these are often shared with other programs.
# Line 371  Cross-compiling on Unix-like systems Line 430  Cross-compiling on Unix-like systems
430  ------------------------------------  ------------------------------------
431    
432  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
433  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
434  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
435  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
436  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,
437  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
438  there are also CXX_FOR_BUILD and CXXFLAGS_FOR_BUILD for the C++ wrapper)  compiler.
439  when calling the "configure" command. If they are not specified, they default  
440  to the values of CC and CFLAGS.  When --enable-rebuild-chartables is not specified, pcre_chartables.c is created
441    by making a copy of pcre_chartables.c.dist, which is a default set of tables
442    that assumes ASCII code. Cross-compiling with the default tables should not be
443    a problem.
444    
445    If you need to modify the character tables when cross-compiling, you should
446    move pcre_chartables.c.dist out of the way, then compile dftables.c by hand and
447    run it on the local host to make a new version of pcre_chartables.c.dist.
448    Then when you cross-compile PCRE this new version of the tables will be used.
449    
450    
451  Using HP's ANSI C++ compiler (aCC)  Using HP's ANSI C++ compiler (aCC)
# Line 401  Making new tarballs Line 468  Making new tarballs
468  -------------------  -------------------
469    
470  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
471  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
472  doc directory, you should first run the PrepareRelease script. This re-creates  build of the new distribution to ensure that it works.
473  the .txt and HTML forms of the documentation from the man pages.  
474    If you have modified any of the man page sources in the doc directory, you
475    should first run the PrepareRelease script before making a distribution. This
476    script creates the .txt and HTML forms of the documentation from the man pages.
477    
478    
479  Testing PCRE  Testing PCRE
# Line 461  is output to say why. If running this te Line 531  is output to say why. If running this te
531  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,
532  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.
533    
534    [If you are trying to run this test on Windows, you may be able to get it to
535    work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
536    RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
537    Windows versions of test 2. More info on using RunTest.bat is included in the
538    document entitled NON-UNIX-USE.]
539    
540  The fourth test checks the UTF-8 support. It is not run automatically unless  The fourth test checks the UTF-8 support. It is not run automatically unless
541  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when
542  running "configure". This file can be also fed directly to the perltest script,  running "configure". This file can be also fed directly to the perltest script,
# Line 490  concatenated tables. A call to pcre_make Line 566  concatenated tables. A call to pcre_make
566  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
567  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.
568    
569  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
570  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
571  (compiled from dftables.c), which uses the ANSI C character handling functions  tables for ASCII coding. However, if --enable-rebuild-chartables is specified
572  such as isalnum(), isalpha(), isupper(), islower(), etc. to build the table  for ./configure, a different version of pcre_chartables.c is built by the
573  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
574  control the contents of these default tables. You can change the default tables  handling functions such as isalnum(), isalpha(), isupper(), islower(), etc. to
575  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
576  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
577    the default tables by editing pcre_chartables.c and then re-building PCRE. If
578    you do this, you should take care to ensure that the file does not get
579    automatically re-generated. The best way to do this is to move
580    pcre_chartables.c.dist out of the way and replace it with your customized
581    tables.
582    
583    When the dftables program is run as a result of --enable-rebuild-chartables,
584    it uses the default C locale that is set on your system. It does not pay
585    attention to the LC_xxx environment variables. In other words, it uses the
586    system's default locale rather than whatever the compiling user happens to have
587    set. If you really do want to build a source set of character tables in a
588    locale that is specified by the LC_xxx variables, you can run the dftables
589    program by hand with the -L option. For example:
590    
591      ./dftables -L pcre_chartables.c.special
592    
593  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,
594  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 526  The distribution should contain the foll Line 617  The distribution should contain the foll
617    
618  (A) Source files of the PCRE library functions and their headers:  (A) Source files of the PCRE library functions and their headers:
619    
620    dftables.c             auxiliary program for building chartables.c    dftables.c              auxiliary program for building pcre_chartables.c
621                                when --enable-rebuild-chartables is specified
622    
623    pcreposix.c            )    pcre_chartables.c.dist  a default set of character tables that assume ASCII
624    pcre_compile.c         )                              coding; used, unless --enable-rebuild-chartables is
625    pcre_config.c          )                              specified, by copying to pcre_chartables.c
626    pcre_dfa_exec.c        )  
627    pcre_exec.c            )    pcreposix.c             )
628    pcre_fullinfo.c        )    pcre_compile.c          )
629    pcre_get.c             ) sources for the functions in the library,    pcre_config.c           )
630    pcre_globals.c         )   and some internal functions that they use    pcre_dfa_exec.c         )
631    pcre_info.c            )    pcre_exec.c             )
632    pcre_maketables.c      )    pcre_fullinfo.c         )
633    pcre_newline.c         )    pcre_get.c              ) sources for the functions in the library,
634    pcre_ord2utf8.c        )    pcre_globals.c          )   and some internal functions that they use
635    pcre_refcount.c        )    pcre_info.c             )
636    pcre_study.c           )    pcre_maketables.c       )
637    pcre_tables.c          )    pcre_newline.c          )
638    pcre_try_flipped.c     )    pcre_ord2utf8.c         )
639    pcre_ucp_searchfuncs.c )    pcre_refcount.c         )
640    pcre_valid_utf8.c      )    pcre_study.c            )
641    pcre_version.c         )    pcre_tables.c           )
642    pcre_xclass.c          )    pcre_try_flipped.c      )
643    pcre_printint.src      ) debugging function that is #included in pcretest,    pcre_ucp_searchfuncs.c  )
644                           )   and can also be #included in pcre_compile()    pcre_valid_utf8.c       )
645    pcre.h.in              template for pcre.h when built by "configure"    pcre_version.c          )
646    pcreposix.h            header for the external POSIX wrapper API    pcre_xclass.c           )
647    pcre_internal.h        header for internal use    pcre_printint.src       ) debugging function that is #included in pcretest,
648    ucp.h                  ) headers concerned with                            )   and can also be #included in pcre_compile()
649    ucpinternal.h          )   Unicode property handling    pcre.h.in               template for pcre.h when built by "configure"
650    ucptable.h             ) (this one is the data table)    pcreposix.h             header for the external POSIX wrapper API
651      pcre_internal.h         header for internal use
652    config.h.in            template for config.h, which is built by "configure"    ucp.h                   ) headers concerned with
653      ucpinternal.h           )   Unicode property handling
654    pcrecpp.h              public header file for the C++ wrapper    ucptable.h              ) (this one is the data table)
655    pcrecpparg.h.in        template for another C++ header file  
656    pcre_scanner.h         public header file for C++ scanner functions    config.h.in             template for config.h, which is built by "configure"
657    pcrecpp.cc             )  
658    pcre_scanner.cc        ) source for the C++ wrapper library    pcrecpp.h               public header file for the C++ wrapper
659      pcrecpparg.h.in         template for another C++ header file
660    pcre_stringpiece.h.in  template for pcre_stringpiece.h, the header for the    pcre_scanner.h          public header file for C++ scanner functions
661                             C++ stringpiece functions    pcrecpp.cc              )
662    pcre_stringpiece.cc    source for the C++ stringpiece functions    pcre_scanner.cc         ) source for the C++ wrapper library
663    
664      pcre_stringpiece.h.in   template for pcre_stringpiece.h, the header for the
665                                C++ stringpiece functions
666      pcre_stringpiece.cc     source for the C++ stringpiece functions
667    
668  (B) Source files for programs that use PCRE:  (B) Source files for programs that use PCRE:
669    
670    pcredemo.c             simple demonstration of coding calls to PCRE    pcredemo.c              simple demonstration of coding calls to PCRE
671    pcregrep.c             source of a grep utility that uses PCRE    pcregrep.c              source of a grep utility that uses PCRE
672    pcretest.c             comprehensive test program    pcretest.c              comprehensive test program
673    
674  (C) Auxiliary files:  (C) Auxiliary files:
675    
676    132html                script to turn "man" pages into HTML    132html                 script to turn "man" pages into HTML
677    AUTHORS                information about the author of PCRE    AUTHORS                 information about the author of PCRE
678    ChangeLog              log of changes to the code    ChangeLog               log of changes to the code
679    CleanTxt               script to clean nroff output for txt man pages    CleanTxt                script to clean nroff output for txt man pages
680    Detrail                script to remove trailing spaces    Detrail                 script to remove trailing spaces
681    Index.html             the base HTML page    HACKING                 some notes about the internals of PCRE
682    INSTALL                generic installation instructions    INSTALL                 generic installation instructions
683    LICENCE                conditions for the use of PCRE    LICENCE                 conditions for the use of PCRE
684    COPYING                the same, using GNU's standard name    COPYING                 the same, using GNU's standard name
685    Makefile.in            ) template for Unix Makefile, which is built by    Makefile.in             ) template for Unix Makefile, which is built by
686                           )   "configure"                            )   "configure"
687    Makefile.am            ) the automake input that was used to create    Makefile.am             ) the automake input that was used to create
688                           )   Makefile.in                            )   Makefile.in
689    NEWS                   important changes in this release    NEWS                    important changes in this release
690    NON-UNIX-USE           notes on building PCRE on non-Unix systems    NON-UNIX-USE            notes on building PCRE on non-Unix systems
691    PrepareRelease         script to make preparations for "make dist"    PrepareRelease          script to make preparations for "make dist"
692    README                 this file    README                  this file
693    RunTest.in             template for a Unix shell script for running tests    RunTest                 a Unix shell script for running tests
694    RunGrepTest.in         template for a Unix shell script for pcregrep tests    RunGrepTest             a Unix shell script for pcregrep tests
695    aclocal.m4             m4 macros (generated by "aclocal")    aclocal.m4              m4 macros (generated by "aclocal")
696    config.guess           ) files used by libtool,    config.guess            ) files used by libtool,
697    config.sub             )   used only when building a shared library    config.sub              )   used only when building a shared library
698    configure              a configuring shell script (built by autoconf)    configure               a configuring shell script (built by autoconf)
699    configure.ac           ) the autoconf input that was used to build    configure.ac            ) the autoconf input that was used to build
700                           )   "configure" and config.h                            )   "configure" and config.h
701    depcomp                ) script to find program dependencies, generated by    depcomp                 ) script to find program dependencies, generated by
702                           )   automake                            )   automake
703    doc/*.3                man page sources for the PCRE functions    doc/*.3                 man page sources for the PCRE functions
704    doc/*.1                man page sources for pcregrep and pcretest    doc/*.1                 man page sources for pcregrep and pcretest
705    doc/html/*             HTML documentation    doc/index.html.src      the base HTML page
706    doc/pcre.txt           plain text version of the man pages    doc/html/*              HTML documentation
707    doc/pcretest.txt       plain text documentation of test program    doc/pcre.txt            plain text version of the man pages
708    doc/perltest.txt       plain text documentation of Perl test program    doc/pcretest.txt        plain text documentation of test program
709    install-sh             a shell script for installing files    doc/perltest.txt        plain text documentation of Perl test program
710    libpcre.pc.in          template for libpcre.pc for pkg-config    install-sh              a shell script for installing files
711    libpcrecpp.pc.in       template for libpcrecpp.pc for pkg-config    libpcre.pc.in           template for libpcre.pc for pkg-config
712    ltmain.sh              file used to build a libtool script    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
713    missing                ) common stub for a few missing GNU programs while    ltmain.sh               file used to build a libtool script
714                           )   installing, generated by automake    missing                 ) common stub for a few missing GNU programs while
715    mkinstalldirs          script for making install directories                            )   installing, generated by automake
716    perltest.pl            Perl test program    mkinstalldirs           script for making install directories
717    pcre-config.in         source of script which retains PCRE information    perltest.pl             Perl test program
718      pcre-config.in          source of script which retains PCRE information
719    pcrecpp_unittest.cc          )    pcrecpp_unittest.cc          )
720    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper    pcre_scanner_unittest.cc     ) test programs for the C++ wrapper
721    pcre_stringpiece_unittest.cc )    pcre_stringpiece_unittest.cc )
722    testdata/testinput*    test data for main library tests    testdata/testinput*     test data for main library tests
723    testdata/testoutput*   expected test results    testdata/testoutput*    expected test results
724    testdata/grep*         input and output for pcregrep tests    testdata/grep*          input and output for pcregrep tests
725    
726  (D) Auxiliary files for cmake support  (D) Auxiliary files for cmake support
727    
# Line 634  The distribution should contain the foll Line 731  The distribution should contain the foll
731  (E) Auxiliary files for VPASCAL  (E) Auxiliary files for VPASCAL
732    
733    makevp.bat    makevp.bat
734    !compile.txt    makevp_c.txt
735    !linklib.txt    makevp_l.txt
736    pcregexp.pas    pcregexp.pas
737    
738  (F) Auxiliary files for building PCRE "by hand"  (F) Auxiliary files for building PCRE "by hand"
739    
740    pcre.h.generic         ) a version of the public PCRE header file    pcre.h.generic          ) a version of the public PCRE header file
741                           )   for use in non-"configure" environments                            )   for use in non-"configure" environments
742    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"
743                           )   environments                            )   environments
744    
745  (F) Miscellaneous  (F) Miscellaneous
746    
# Line 652  The distribution should contain the foll Line 749  The distribution should contain the foll
749  Philip Hazel  Philip Hazel
750  Email local part: ph10  Email local part: ph10
751  Email domain: cam.ac.uk  Email domain: cam.ac.uk
752  Last updated: March 2007  Last updated: 13 April 2008

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

  ViewVC Help
Powered by ViewVC 1.1.5