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

Diff of /code/trunk/README

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

revision 149 by ph10, Mon Apr 16 15:28:08 2007 UTC revision 286 by ph10, Mon Dec 17 14:46:11 2007 UTC
# Line 103  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 184  library. You can read more about them in Line 186  library. You can read more about them in
186    --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
187    failures.    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 in a pattern. You can increase this threshold by setting, for example,    them in a pattern. You can increase this threshold by setting, for example,
# Line 250  library. You can read more about them in Line 258  library. You can read more about them in
258    
259    This automatically implies --enable-rebuild-chartables (see above).    This automatically implies --enable-rebuild-chartables (see above).
260    
261    . It is possible to compile pcregrep to use libz and/or libbz2 to read .gz
262      and .bz2 files (respectively) by specifying one or both of
263    
264      --enable-pcregrep-libz
265      --enable-pcregrep-libbz2
266    
267  The "configure" script builds the following files for the basic C library:  The "configure" script builds the following files for the basic C library:
268    
269  . Makefile is the makefile that builds the library  . Makefile is the makefile that builds the library
# Line 436  Making new tarballs Line 450  Making new tarballs
450  -------------------  -------------------
451    
452  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
453  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
454  doc directory, you should first run the PrepareRelease script. This re-creates  build of the new distribution to ensure that it works.
455  the .txt and HTML forms of the documentation from the man pages.  
456    If you have modified any of the man page sources in the doc directory, you
457    should first run the PrepareRelease script before making a distribution. This
458    script creates the .txt and HTML forms of the documentation from the man pages.
459    
460    
461  Testing PCRE  Testing PCRE
# Line 497  in the comparison output, it means that Line 514  in the comparison output, it means that
514  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.
515    
516  [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
517  work by changing "fr_FR" to "french" everywhere it occurs.]  work by changing "fr_FR" to "french" everywhere it occurs. Alternatively, use
518    RunTest.bat. The version of RunTest.bat included with PCRE 7.4 and above uses
519    Windows versions of test 2. More info on using RunTest.bat is included in the
520    document entitled NON-UNIX-USE.]
521    
522  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
523  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
# Line 711  The distribution should contain the foll Line 731  The distribution should contain the foll
731  Philip Hazel  Philip Hazel
732  Email local part: ph10  Email local part: ph10
733  Email domain: cam.ac.uk  Email domain: cam.ac.uk
734  Last updated: 16 April 2007  Last updated: 17 December 2007

Legend:
Removed from v.149  
changed lines
  Added in v.286

  ViewVC Help
Powered by ViewVC 1.1.5