|
version 1.1.1.2, 2012/02/21 23:50:25
|
version 1.1.1.3, 2012/10/09 09:19:17
|
|
Line 18 The contents of this README file are:
|
Line 18 The contents of this README file are:
|
| The PCRE APIs |
The PCRE APIs |
| Documentation for PCRE |
Documentation for PCRE |
| Contributions by users of PCRE |
Contributions by users of PCRE |
| Building PCRE on non-Unix systems | Building PCRE on non-Unix-like systems |
| Building PCRE on Unix-like systems | Building PCRE without using autotools |
| Retrieving configuration information on Unix-like systems | Building PCRE using autotools |
| Shared libraries on Unix-like systems | Retrieving configuration information |
| Cross-compiling on Unix-like systems | Shared libraries |
| | Cross-compiling using autotools |
| Using HP's ANSI C++ compiler (aCC) |
Using HP's ANSI C++ compiler (aCC) |
| Using PCRE from MySQL |
Using PCRE from MySQL |
| Making new tarballs |
Making new tarballs |
|
Line 109 Windows (I myself do not use Windows). Nowadays there
|
Line 110 Windows (I myself do not use Windows). Nowadays there
|
| in the standard distribution, so these contibutions have been archived. |
in the standard distribution, so these contibutions have been archived. |
| |
|
| |
|
| Building PCRE on non-Unix systems | Building PCRE on non-Unix-like systems |
| --------------------------------- | -------------------------------------- |
| |
|
| 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 |
| 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 |
| 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 |
| configured in many platform environments using the GUI facility provided by | many Unix-like systems. |
| CMake's cmake-gui command. This creates Makefiles, solution files, etc. | |
| |
|
| |
PCRE can also be configured using the GUI facility provided by CMake's |
| |
cmake-gui command. This creates Makefiles, solution files, etc. The file |
| |
NON-AUTOTOOLS-BUILD has information about CMake. |
| |
|
| PCRE has been compiled on many different operating systems. It should be |
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 |
straightforward to build PCRE on any system that has a Standard C compiler and |
| library, because it uses only Standard C functions. |
library, because it uses only Standard C functions. |
| |
|
| |
|
| Building PCRE on Unix-like systems | Building PCRE without using autotools |
| ---------------------------------- | ------------------------------------- |
| |
|
| |
The use of autotools (in particular, libtool) is problematic in some |
| |
environments, even some that are Unix or Unix-like. See the NON-AUTOTOOLS-BUILD |
| |
file for ways of building PCRE without using autotools. |
| |
|
| |
|
| |
Building PCRE using autotools |
| |
----------------------------- |
| |
|
| 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 |
| in the section entitled "Using HP's ANSI C++ compiler (aCC)" below. |
in the section entitled "Using HP's ANSI C++ compiler (aCC)" below. |
| |
|
| The following instructions assume the use of the widely used "configure, make, | The following instructions assume the use of the widely used "configure; make; |
| make install" process. There is also support for CMake in the PCRE | make install" (autotools) process. |
| distribution; there are some comments about using CMake in the NON-UNIX-USE | |
| file, though it can also be used in Unix-like systems. | |
| |
|
| To build PCRE on a Unix-like system, first run the "configure" command from the | To build PCRE on system that supports autotools, first run the "configure" |
| PCRE distribution directory, with your current directory set to the directory | command from the PCRE distribution directory, with your current directory set |
| where you want the files to be created. This command is a standard GNU | to the directory where you want the files to be created. This command is a |
| "autoconf" configuration script, for which generic instructions are supplied in | standard GNU "autoconf" configuration script, for which generic instructions |
| the file INSTALL. | are supplied in the file INSTALL. |
| |
|
| Most commonly, people build PCRE within its own distribution directory, and in |
Most commonly, people build PCRE within its own distribution directory, and in |
| this case, on many systems, just running "./configure" is sufficient. However, |
this case, on many systems, just running "./configure" is sufficient. However, |
|
Line 326 library. They are also documented in the pcrebuild man
|
Line 336 library. They are also documented in the pcrebuild man
|
| The default value is 20K. |
The default value is 20K. |
| |
|
| . 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 |
| library, by specifying | or libedit libraries, by specifying, respectively, |
| |
|
| --enable-pcretest-libreadline | --enable-pcretest-libreadline or --enable-pcretest-libedit |
| |
|
| 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 |
| the readline() function. This provides line-editing and history facilities. |
the readline() function. This provides line-editing and history facilities. |
| 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 |
| pcretest linked in this way, there may be licensing issues. | pcretest linked in this way, there may be licensing issues. These can be |
| | avoided by linking with libedit (which has a BSD licence) instead. |
| |
|
| 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 |
| build. In many operating environments with a sytem-installed readline |
build. In many operating environments with a sytem-installed readline |
| library this is sufficient. However, in some environments (e.g. if an |
library this is sufficient. However, in some environments (e.g. if an |
| 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 357 The "configure" script builds the following files for
|
Line 368 The "configure" script builds the following files for
|
| . libpcre16.pc ) |
. libpcre16.pc ) |
| . libpcreposix.pc ) |
. libpcreposix.pc ) |
| . 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 |
|
| |
|
| 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 |
| 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 447 This removes all the files that "make install" install
|
Line 456 This removes all the files that "make install" install
|
| remove any directories, because these are often shared with other programs. |
remove any directories, because these are often shared with other programs. |
| |
|
| |
|
| Retrieving configuration information on Unix-like systems | Retrieving configuration information |
| --------------------------------------------------------- | ------------------------------------ |
| |
|
| 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 |
| 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 installed in a
|
Line 482 The data is held in *.pc files that are installed in a
|
| <prefix>/lib/pkgconfig. |
<prefix>/lib/pkgconfig. |
| |
|
| |
|
| Shared libraries on Unix-like systems | Shared libraries |
| ------------------------------------- | ---------------- |
| |
|
| The default distribution builds PCRE as shared libraries and static libraries, |
The default distribution builds PCRE as shared libraries and static libraries, |
| 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. Similarly, you can u
|
Line 508 Then run "make" in the usual way. Similarly, you can u
|
| build only shared libraries. |
build only shared libraries. |
| |
|
| |
|
| Cross-compiling on Unix-like systems | Cross-compiling using autotools |
| ------------------------------------ | ------------------------------- |
| |
|
| 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 |
| 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 of the document
|
Line 581 script creates the .txt and HTML forms of the document
|
| Testing PCRE |
Testing PCRE |
| ------------ |
------------ |
| |
|
| 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. |
| created by the configuring process. There is also a script called RunGrepTest | There is another script called RunGrepTest that tests the options of the |
| 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 |
| built, three test programs called pcrecpp_unittest, pcre_scanner_unittest, and | called pcrecpp_unittest, pcre_scanner_unittest, and pcre_stringpiece_unittest |
| pcre_stringpiece_unittest are also built. When JIT support is enabled, another | are also built. When JIT support is enabled, another test program called |
| test program called pcre_jit_test is built. | pcre_jit_test is built. |
| |
|
| 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 |
| "make test". For other systems, see the instructions in NON-UNIX-USE. | "make test". For other environments, see the instructions in |
| | NON-AUTOTOOLS-BUILD. |
| |
|
| 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 |
| 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 |
|
Line 606 numbers as arguments to RunTest, for example:
|
Line 616 numbers as arguments to RunTest, for example:
|
| |
|
| RunTest 2 7 11 |
RunTest 2 7 11 |
| |
|
| |
You can also call RunTest with the single argument "list" to cause it to output |
| |
a list of tests. |
| |
|
| 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 |
| 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 |
| 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 811 pcre_xxx and the other with the name pcre16_xxx.
|
Line 824 pcre_xxx and the other with the name pcre16_xxx.
|
| Makefile.am ) the automake input that was used to create |
Makefile.am ) the automake input that was used to create |
| ) Makefile.in |
) Makefile.in |
| NEWS important changes in this release |
NEWS important changes in this release |
| NON-UNIX-USE notes on building PCRE on non-Unix systems | NON-UNIX-USE the previous name for NON-AUTOTOOLS-BUILD |
| | NON-AUTOTOOLS-BUILD notes on building PCRE without using autotools |
| PrepareRelease script to make preparations for "make dist" |
PrepareRelease script to make preparations for "make dist" |
| README this file |
README this file |
| RunTest a Unix shell script for running tests |
RunTest a Unix shell script for running tests |
|
Line 855 pcre_xxx and the other with the name pcre16_xxx.
|
Line 869 pcre_xxx and the other with the name pcre16_xxx.
|
| |
|
| cmake/COPYING-CMAKE-SCRIPTS |
cmake/COPYING-CMAKE-SCRIPTS |
| cmake/FindPackageHandleStandardArgs.cmake |
cmake/FindPackageHandleStandardArgs.cmake |
| |
cmake/FindEditline.cmake |
| cmake/FindReadline.cmake |
cmake/FindReadline.cmake |
| CMakeLists.txt |
CMakeLists.txt |
| config-cmake.h.in |
config-cmake.h.in |
|
Line 880 pcre_xxx and the other with the name pcre16_xxx.
|
Line 895 pcre_xxx and the other with the name pcre16_xxx.
|
| Philip Hazel |
Philip Hazel |
| Email local part: ph10 |
Email local part: ph10 |
| Email domain: cam.ac.uk |
Email domain: cam.ac.uk |
| Last updated: 20 January 2012 | Last updated: 18 June 2012 |
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to README CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / pcre