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

Diff of /code/trunk/README

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

revision 376 by ph10, Sun Mar 1 12:00:59 2009 UTC revision 452 by ph10, Wed Sep 16 19:18:51 2009 UTC
# Line 24  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 85  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 107  Building PCRE on non-Unix systems Line 112  Building PCRE on non-Unix systems
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. PCRE can also be  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 of CMake's  configured in many platform environments using the GUI facility provided by
116  CMakeSetup. It creates Makefiles, solution files, etc.  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 161  library. You can read more about them in Line 166  library. You can read more about them in
166    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,
167    it will try to build the C++ wrapper.    it will try to build the C++ wrapper.
168    
169  . 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 Unicode character strings in
170    you must add --enable-utf8 to the "configure" command. Without it, the code    PCRE, you must add --enable-utf8 to the "configure" command. Without it, the
171    for handling UTF-8 is not included in the library. (Even when included, it    code for handling UTF-8 is not included in the library. Even when included,
172    still has to be enabled by an option at run time.)    it still has to be enabled by an option at run time. When PCRE is compiled
173      with this option, its input can only either be ASCII or UTF-8, even when
174      running on EBCDIC platforms. It is not possible to use both --enable-utf8 and
175      --enable-ebcdic at the same time.
176    
177  . 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
178    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 255  library. You can read more about them in Line 263  library. You can read more about them in
263    pcre_chartables.c.dist. See "Character tables" below for further information.    pcre_chartables.c.dist. See "Character tables" below for further information.
264    
265  . 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
266    default character code (as opposed to ASCII) by specifying    character code (as opposed to ASCII) by specifying
267    
268    --enable-ebcdic    --enable-ebcdic
269    
270    This automatically implies --enable-rebuild-chartables (see above).    This automatically implies --enable-rebuild-chartables (see above). However,
271      when PCRE is built this way, it always operates in EBCDIC. It cannot support
272      both EBCDIC and UTF-8.
273    
274  . It is possible to compile pcregrep to use libz and/or libbz2, in order to  . It is possible to compile pcregrep to use libz and/or libbz2, in order to
275    read .gz and .bz2 files (respectively), by specifying one or both of    read .gz and .bz2 files (respectively), by specifying one or both of
# Line 286  library. You can read more about them in Line 296  library. You can read more about them in
296    to specify something like LIBS="-lncurses" as well. This is because, to quote    to specify something like LIBS="-lncurses" as well. This is because, to quote
297    the readline INSTALL, "Readline uses the termcap functions, but does not link    the readline INSTALL, "Readline uses the termcap functions, but does not link
298    with the termcap or curses library itself, allowing applications which link    with the termcap or curses library itself, allowing applications which link
299    with readline the to choose an appropriate library." If you get error    with readline the to choose an appropriate library." If you get error
300    messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,    messages about missing functions tgetstr, tgetent, tputs, tgetflag, or tgoto,
301    this is the problem, and linking with the ncurses library should fix it.    this is the problem, and linking with the ncurses library should fix it.
302    
303  The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
304    
# Line 467  use the workaround of specifying the fol Line 477  use the workaround of specifying the fol
477  running the "configure" script:  running the "configure" script:
478    
479    CXXLDFLAGS="-lstd_v2 -lCsup_v2"    CXXLDFLAGS="-lstd_v2 -lCsup_v2"
480    
481    
482    Using PCRE from MySQL
483    ---------------------
484    
485    On systems where both PCRE and MySQL are installed, it is possible to make use
486    of PCRE from within MySQL, as an alternative to the built-in pattern matching.
487    There is a web page that tells you how to do this:
488    
489      http://www.mysqludf.org/lib_mysqludf_preg/index.php
490    
491    
492  Making new tarballs  Making new tarballs
# Line 703  The distribution should contain the foll Line 723  The distribution should contain the foll
723                            )   "configure" and config.h                            )   "configure" and config.h
724    depcomp                 ) script to find program dependencies, generated by    depcomp                 ) script to find program dependencies, generated by
725                            )   automake                            )   automake
726    doc/*.3                 man page sources for the PCRE functions    doc/*.3                 man page sources for PCRE
727    doc/*.1                 man page sources for pcregrep and pcretest    doc/*.1                 man page sources for pcregrep and pcretest
728    doc/index.html.src      the base HTML page    doc/index.html.src      the base HTML page
729    doc/html/*              HTML documentation    doc/html/*              HTML documentation
# Line 712  The distribution should contain the foll Line 732  The distribution should contain the foll
732    doc/perltest.txt        plain text documentation of Perl test program    doc/perltest.txt        plain text documentation of Perl test program
733    install-sh              a shell script for installing files    install-sh              a shell script for installing files
734    libpcre.pc.in           template for libpcre.pc for pkg-config    libpcre.pc.in           template for libpcre.pc for pkg-config
735      libpcreposix.pc.in      template for libpcreposix.pc for pkg-config
736    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config    libpcrecpp.pc.in        template for libpcrecpp.pc for pkg-config
737    ltmain.sh               file used to build a libtool script    ltmain.sh               file used to build a libtool script
738    missing                 ) common stub for a few missing GNU programs while    missing                 ) common stub for a few missing GNU programs while
# Line 755  The distribution should contain the foll Line 776  The distribution should contain the foll
776  Philip Hazel  Philip Hazel
777  Email local part: ph10  Email local part: ph10
778  Email domain: cam.ac.uk  Email domain: cam.ac.uk
779  Last updated: 27 February 2009  Last updated: 16 September 2009

Legend:
Removed from v.376  
changed lines
  Added in v.452

  ViewVC Help
Powered by ViewVC 1.1.5