/[pcre]/code/trunk/README

Diff of /code/trunk/README

Parent Directory | Revision Log | View Patch Patch

-revision 135 by ph10,
Thu Mar 29 09:09:33 2007 UTC
+revision 312 by ph10,
Wed Jan 23 18:02:23 2008 UTC
 Line 103 
 Building PCRE on non-Unix systems
  For a non-Unix system, please read the comments in the file NON-UNIX-USE,
  though if your system supports the use of "configure" and "make" you may be
- 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
+ configured in many platform environments using the GUI facility of CMake's
+ CMakeSetup. It creates Makefiles, solution files, etc.
  PCRE has been compiled on many different operating systems. It should be
  straightforward to build PCRE on any system that has a Standard C compiler and
-Line 116 
 Building PCRE on Unix-like systems
+Line 118 
 Building PCRE on Unix-like systems
  If you are using HP's ANSI C++ compiler (aCC), please see the special note
  in the section entitled "Using HP's ANSI C++ compiler (aCC)" below.
+ The following instructions assume the use of the widely used "configure, make,
+ make install" process. There is also some experimental support for "cmake" in
+ the PCRE distribution, but it is incomplete and not documented. However, if you
+ are a "cmake" user, you might want to try it.
  To build PCRE on a Unix-like system, first run the "configure" command from the
  PCRE distribution directory, with your current directory set to the directory
  where you want the files to be created. This command is a standard GNU
-Line 164 
 library. You can read more about them in
+Line 171 
 library. You can read more about them in
    supported.
  . You can build PCRE to recognize either CR or LF or the sequence CRLF or any
-   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
-   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
-   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
-   (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
-   --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
-   to the "configure" command, respectively.
+   or --enable-newline-is-crlf or --enable-newline-is-anycrlf or
+   --enable-newline-is-any to the "configure" command, respectively.
-   If you specify --newline-is-cr or --newline-is-crlf, some of the standard
-   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
-   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
-   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
-   some failures.
+   to be some failures. With --enable-newline-is-anycrlf or
+   --enable-newline-is-any, many tests should succeed, but there may be some
+   failures.
+ . By default, the sequence \R in a pattern matches any Unicode line ending
+   sequence. This is independent of the option specifying what PCRE considers to
+   be the end of a line (see above). However, the caller of PCRE can restrict \R
+   to match only CR, LF, or CRLF. You can make this the default by adding
+   --enable-bsr-anycrlf to the "configure" command (bsr = "backslash R").
  . When called via the POSIX interface, PCRE uses malloc() to get additional
    storage for processing capturing parentheses if there are more than 10 of
-Line 243 
 library. You can read more about them in
+Line 258 
 library. You can read more about them in
    This automatically implies --enable-rebuild-chartables (see above).
+ . It is possible to compile pcregrep to use libz and/or libbz2, in order to
+   read .gz and .bz2 files (respectively), by specifying one or both of
+   --enable-pcregrep-libz
+   --enable-pcregrep-libbz2
+   Of course, the relevant libraries must be installed on your system.
+ . It is possible to compile pcretest so that it links with the libreadline
+   library, by specifying
+   --enable-pcretest-libreadline
+   If this is done, when pcretest's input is from a terminal, it reads it using
+   the readline() function. This provides line-editing and history facilities.
+   Note that libreadline is GPL-licenced, so if you distribute a binary of
+   pcretest linked in this way, there may be licensing issues.
  The "configure" script builds the following files for the basic C library:
  . Makefile is the makefile that builds the library
-Line 270 
 script that can be run to recreate the c
+Line 303 
 script that can be run to recreate the c
  contains compiler output from tests that "configure" runs.
  Once "configure" has run, you can run "make". It builds two libraries, called
- libpcre and libpcreposix, a test program called pcretest, a demonstration
+ libpcre and libpcreposix, a test program called pcretest, and the pcregrep
- 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++
- on your system, "make" also builds the C++ wrapper library, which is called
+ wrapper library, which is called libpcrecpp, and some test programs called
- libpcrecpp, and some test programs called pcrecpp_unittest,
+ pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest.
- pcre_scanner_unittest, and pcre_stringpiece_unittest. Building the C++ wrapper
+ Building the C++ wrapper can be disabled by adding --disable-cpp to the
- can be disabled by adding --disable-cpp to the "configure" command.
+ "configure" command.
  The command "make check" runs all the appropriate tests. Details of the PCRE
  tests are given below in a separate section of this document.
-Line 327 
 system. The following are installed (fil
+Line 360 
 system. The following are installed (fil
      pcretest.txt   the pcretest man page
      pcregrep.txt   the pcregrep 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.
  If you want to remove PCRE from your system, you can run "make uninstall".
  This removes all the files that "make install" installed. However, it does not
  remove any directories, because these are often shared with other programs.
-Line 429 
 Making new tarballs
+Line 459 
 Making new tarballs
  -------------------
  The command "make dist" creates three PCRE tarballs, in tar.gz, tar.bz2, and
- 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
- doc directory, you should first run the PrepareRelease script. This re-creates
+ build of the new distribution to ensure that it works.
- the .txt and HTML forms of the documentation from the man pages.
+ If you have modified any of the man page sources in the doc directory, you
+ should first run the PrepareRelease script before making a distribution. This
+ script creates the .txt and HTML forms of the documentation from the man pages.
  Testing PCRE
-Line 489 
 is output to say why. If running this te
+Line 522 
 is output to say why. If running this te
  in the comparison output, it means that locale is not available on your system,
  despite being listed by "locale". This does not mean that PCRE is broken.
+ [If you are trying to run this test on Windows, you may be able to get it to
+ work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
+ RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
+ Windows versions of test 2. More info on using RunTest.bat is included in the
+ document entitled NON-UNIX-USE.]
  The fourth test checks the UTF-8 support. It is not run automatically unless
  PCRE is built with UTF-8 support. To do this you must set --enable-utf8 when
  running "configure". This file can be also fed directly to the perltest script,
-Line 642 
 The distribution should contain the foll
+Line 681 
 The distribution should contain the foll
    NON-UNIX-USE            notes on building PCRE on non-Unix systems
    PrepareRelease          script to make preparations for "make dist"
    README                  this file
-   RunTest.in              template for a Unix shell script for running tests
+   RunTest                 a Unix shell script for running tests
-   RunGrepTest.in          template for a Unix shell script for pcregrep tests
+   RunGrepTest             a Unix shell script for pcregrep tests
    aclocal.m4              m4 macros (generated by "aclocal")
    config.guess            ) files used by libtool,
    config.sub              )   used only when building a shared library
-Line 701 
 The distribution should contain the foll
+Line 740 
 The distribution should contain the foll
  Philip Hazel
  Email local part: ph10
  Email domain: cam.ac.uk
- Last updated: 26 March 2007
+ Last updated: 23 January 2008

 Legend:



Removed from v.135
 


changed lines


 
Added in v.312
 Legend:



Removed from v.135
 


changed lines


 
Added in v.312
-Removed from v.135
+Added in v.312

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12