/[pcre]/code/trunk/NON-UNIX-USE

Diff of /code/trunk/NON-UNIX-USE

Parent Directory | Revision Log | View Patch Patch

-revision 122 by ph10,
Mon Mar 12 15:10:25 2007 UTC
+revision 672 by ph10,
Tue Aug 23 16:45:55 2011 UTC
 Line 1
  Compiling PCRE on non-Unix systems
  ----------------------------------
- I (Philip Hazel) have no knowledge of Windows or VMS sytems and how their
+ This document contains the following sections:
+   General
+   Generic instructions for the PCRE C library
+   The C++ wrapper functions
+   Building for virtual Pascal
+   Stack size in Windows environments
+   Linking programs in Windows environments
+   Comments about Win32 builds
+   Building PCRE on Windows with CMake
+   Use of relative paths with CMake on Windows
+   Testing with RunTest.bat
+   Building under Windows with BCC5.5
+   Building PCRE on OpenVMS
+   Building PCRE on Stratus OpenVOS
+ GENERAL
+ I (Philip Hazel) have no experience of Windows or VMS sytems and how their
  libraries work. The items in the PCRE distribution and Makefile that relate to
  anything other than Unix-like systems are untested by me.
- There are some other comments and files in the Contrib directory on the ftp
+ There are some other comments and files (including some documentation in CHM
- site that you may find useful, although a lot of them are now out-of-date. See
+ format) in the Contrib directory on the FTP site:
    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
- If you want to compile PCRE for a non-Unix system (or perhaps, more strictly,
+ If you want to compile PCRE for a non-Unix system (especially for a system that
- for a system that does not support "configure" and "make" files), note that
+ does not support "configure" and "make" files), note that the basic PCRE
- the basic PCRE library consists entirely of code written in Standard C, and so
+ library consists entirely of code written in Standard C, and so should compile
- should compile successfully on any system that has a Standard C compiler and
+ successfully on any system that has a Standard C compiler and library. The C++
- library. The C++ wrapper functions are a separate issue (see below).
+ wrapper functions are a separate issue (see below).
+ The PCRE distribution includes a "configure" file for use by the Configure/Make
- GENERIC INSTRUCTIONS FOR THE C LIBRARY
+ build system, as found in many Unix-like environments. There is also support
+ for CMake, which some users prefer, especially in Windows environments. There
- The following are generic comments about building the PCRE C library "by hand".
+ are some instructions for CMake under Windows in the section entitled "Building
+ PCRE with CMake" below. CMake can also be used to build PCRE in Unix-like
- (1) Copy or rename the file config.h.generic as config.h, and edit the macro
+ systems.
-     settings that it contains to whatever is appropriate for your environment.
-     In particular, if you want to force a specific value for newline, you can
-     define the NEWLINE macro.
+ GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
-     An alternative approach is not to edit config.h, but to use -D on the
+ The following are generic instructions for building the PCRE C library "by
-     compiler command line to make any changes that you need.
+ hand":
- (2) Copy or rename the file pcre.h.generic as pcre.h.
+  (1) Copy or rename the file config.h.generic as config.h, and edit the macro
+      settings that it contains to whatever is appropriate for your environment.
- (3) Compile dftables.c as a stand-alone program, and then run it with
+      In particular, if you want to force a specific value for newline, you can
-     the single argument "pcre_chartables.c". This generates a set of standard
+      define the NEWLINE macro. When you compile any of the PCRE modules, you
-     character tables and writes them to that file.
+      must specify -DHAVE_CONFIG_H to your compiler so that config.h is included
+      in the sources.
- (4) Compile the following source files:
+      An alternative approach is not to edit config.h, but to use -D on the
-       pcre_chartables.c
+      compiler command line to make any changes that you need to the
-       pcre_compile.c
+      configuration options. In this case -DHAVE_CONFIG_H must not be set.
-       pcre_config.c
-       pcre_dfa_exec.c
+      NOTE: There have been occasions when the way in which certain parameters
-       pcre_exec.c
+      in config.h are used has changed between releases. (In the configure/make
-       pcre_fullinfo.c
+      world, this is handled automatically.) When upgrading to a new release,
-       pcre_get.c
+      you are strongly advised to review config.h.generic before re-using what
-       pcre_globals.c
+      you had previously.
-       pcre_info.c
-       pcre_maketables.c
+  (2) Copy or rename the file pcre.h.generic as pcre.h.
-       pcre_newline.c
-       pcre_ord2utf8.c
+  (3) EITHER:
-       pcre_refcount.c
+        Copy or rename file pcre_chartables.c.dist as pcre_chartables.c.
-       pcre_study.c
-       pcre_tables.c
+      OR:
-       pcre_try_flipped.c
+        Compile dftables.c as a stand-alone program (using -DHAVE_CONFIG_H if
-       pcre_ucp_searchfuncs.c
+        you have set up config.h), and then run it with the single argument
-       pcre_valid_utf8.c
+        "pcre_chartables.c". This generates a set of standard character tables
-       pcre_version.c
+        and writes them to that file. The tables are generated using the default
-       pcre_xclass.c
+        C locale for your system. If you want to use a locale that is specified
+        by LC_xxx environment variables, add the -L option to the dftables
-     Now link them all together into an object library in whichever form your
+        command. You must use this method if you are building on a system that
-     system keeps such libraries. This is the basic PCRE C library. If your
+        uses EBCDIC code.
-     system has static and shared libraries, you may have to do this once for
-     each type.
+      The tables in pcre_chartables.c are defaults. The caller of PCRE can
+      specify alternative tables at run time.
- (5) Similarly, compile pcreposix.c and link it (on its own) as the pcreposix
-     library.
+  (4) Ensure that you have the following header files:
- (6) Compile the test program pcretest.c. This needs the functions in the
+        pcre_internal.h
-     pcre and pcreposix libraries when linking.
+        ucp.h
- (7) Run pcretest on the testinput files in the testdata directory, and check
+  (5) Also ensure that you have the following file, which is #included as source
-     that the output matches the corresponding testoutput files. Note that the
+      when building a debugging version of PCRE, and is also used by pcretest.
-     supplied files are in Unix format, with just LF characters as line
-     terminators. You may need to edit them to change this if your system uses a
+        pcre_printint.src
-     different convention.
+  (6) Compile the following source files, setting -DHAVE_CONFIG_H as a compiler
+      option if you have set up config.h with your configuration, or else use
+      other -D settings to change the configuration as required.
+        pcre_chartables.c
+        pcre_compile.c
+        pcre_config.c
+        pcre_dfa_exec.c
+        pcre_exec.c
+        pcre_fullinfo.c
+        pcre_get.c
+        pcre_globals.c
+        pcre_info.c
+        pcre_maketables.c
+        pcre_newline.c
+        pcre_ord2utf8.c
+        pcre_refcount.c
+        pcre_study.c
+        pcre_tables.c
+        pcre_try_flipped.c
+        pcre_ucd.c
+        pcre_valid_utf8.c
+        pcre_version.c
+        pcre_xclass.c
+      Make sure that you include -I. in the compiler command (or equivalent for
+      an unusual compiler) so that all included PCRE header files are first
+      sought in the current directory. Otherwise you run the risk of picking up
+      a previously-installed file from somewhere else.
+  (7) If you have defined SUPPORT_JIT in config.h, you must also compile
+        pcre_jit_compile.c
+      This file #includes sources from the sljit subdirectory, where there
+      should be 16 files, all of whose names begin with "sljit".
+  (8) Now link all the compiled code into an object library in whichever form
+      your system keeps such libraries. This is the basic PCRE C library. If
+      your system has static and shared libraries, you may have to do this once
+      for each type.
+  (9) Similarly, if you want to build the POSIX wrapper functions, ensure that
+      you have the pcreposix.h file and then compile pcreposix.c (remembering
+      -DHAVE_CONFIG_H if necessary). Link the result (on its own) as the
+      pcreposix library.
+ (10) Compile the test program pcretest.c (again, don't forget -DHAVE_CONFIG_H).
+      This needs the functions in the PCRE library when linking. It also needs
+      the pcreposix wrapper functions unless you compile it with -DNOPOSIX. The
+      pcretest.c program also needs the pcre_printint.src source file, which it
+      #includes.
+ (11) Run pcretest on the testinput files in the testdata directory, and check
+      that the output matches the corresponding testoutput files. Some tests are
+      relevant only when certain build-time options are selected. For example,
+      test 4 is for UTF-8 support, and will not run if you have build PCRE
+      without it. See the comments at the start of each testinput file. If you
+      have a suitable Unix-like shell, the RunTest script will run the
+      appropriate tests for you.
+      Note that the supplied files are in Unix format, with just LF characters
+      as line terminators. You may need to edit them to change this if your
+      system uses a different convention. If you are using Windows, you probably
+      should use the wintestinput3 file instead of testinput3 (and the
+      corresponding output file). This is a locale test; wintestinput3 sets the
+      locale to "french" rather than "fr_FR", and there some minor output
+      differences.
+ (12) If you have built PCRE with SUPPORT_JIT, the JIT features will be tested
+      by the testdata files. However, you might also like to build and run
+      the JIT test program, pcre_jit_test.c.
- (8) If you want to use the pcregrep command, compile and link pcregrep.c; it
+ (13) If you want to use the pcregrep command, compile and link pcregrep.c; it
-     uses only the basic PCRE library (it does not need the pcreposix library).
+      uses only the basic PCRE library (it does not need the pcreposix library).
  THE C++ WRAPPER FUNCTIONS
-Line 91 
 xxx.cc files.
+Line 182 
 xxx.cc files.
  BUILDING FOR VIRTUAL PASCAL
- Stefan Weber contributed the following files in the distribution for building
+ A script for building PCRE using Borland's C++ compiler for use with VPASCAL
- PCRE for use with VP/Borland: !compile.txt, !linklib.txt, makevp.bat,
+ was contributed by Alexander Tokarev. Stefan Weber updated the script and added
- pcregexp.pas.
+ additional files. The following files in the distribution are for building PCRE
+ for use with VP/Borland: makevp_c.txt, makevp_l.txt, makevp.bat, pcregexp.pas.
+ STACK SIZE IN WINDOWS ENVIRONMENTS
+ The default processor stack size of 1Mb in some Windows environments is too
+ small for matching patterns that need much recursion. In particular, test 2 may
+ fail because of this. Normally, running out of stack causes a crash, but there
+ have been cases where the test program has just died silently. See your linker
+ documentation for how to increase stack size if you experience problems. The
+ Linux default of 8Mb is a reasonable choice for the stack, though even that can
+ be too small for some pattern/subject combinations.
+ PCRE has a compile configuration option to disable the use of stack for
+ recursion so that heap is used instead. However, pattern matching is
+ significantly slower when this is done. There is more about stack usage in the
+ "pcrestack" documentation.
+ LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
+ If you want to statically link a program against a PCRE library in the form of
+ a non-dll .a file, you must define PCRE_STATIC before including pcre.h or
+ pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will
+ be declared __declspec(dllimport), with unwanted results.
+ CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS
+ It is possible to compile programs to use different calling conventions using
+ MSVC. Search the web for "calling conventions" for more information. To make it
+ easier to change the calling convention for the exported functions in the
+ PCRE library, the macro PCRE_CALL_CONVENTION is present in all the external
+ definitions. It can be set externally when compiling (e.g. in CFLAGS). If it is
+ not set, it defaults to empty; the default calling convention is then used
+ (which is what is wanted most of the time).
+ COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE WITH CMAKE" below)
+ There are two ways of building PCRE using the "configure, make, make install"
+ paradigm on Windows systems: using MinGW or using Cygwin. These are not at all
+ the same thing; they are completely different from each other. There is also
+ support for building using CMake, which some users find a more straightforward
+ way of building PCRE under Windows. However, the tests are not run
+ automatically when CMake is used.
+ The MinGW home page (http://www.mingw.org/) says this:
+   MinGW: A collection of freely available and freely distributable Windows
+   specific header files and import libraries combined with GNU toolsets that
+   allow one to produce native Windows programs that do not rely on any
+rd-party C runtime DLLs.
+ The Cygwin home page (http://www.cygwin.com/) says this:
+   Cygwin is a Linux-like environment for Windows. It consists of two parts:
+   . A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing
+     substantial Linux API functionality
+   . A collection of tools which provide Linux look and feel.
+   The Cygwin DLL currently works with all recent, commercially released x86 32
+   bit and 64 bit versions of Windows, with the exception of Windows CE.
+ On both MinGW and Cygwin, PCRE should build correctly using:
+   ./configure && make && make install
+ This should create two libraries called libpcre and libpcreposix, and, if you
+ have enabled building the C++ wrapper, a third one called libpcrecpp. These are
+ independent libraries: when you link with libpcreposix or libpcrecpp you must
+ also link with libpcre, which contains the basic functions. (Some earlier
+ releases of PCRE included the basic libpcre functions in libpcreposix. This no
+ longer happens.)
+ A user submitted a special-purpose patch that makes it easy to create
+ "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"
+ as a special target. If you use this target, no other files are built, and in
+ particular, the pcretest and pcregrep programs are not built. An example of how
+ this might be used is:
+   ./configure --enable-utf --disable-cpp CFLAGS="-03 -s"; make pcre.dll
+ Using Cygwin's compiler generates libraries and executables that depend on
+ cygwin1.dll. If a library that is generated this way is distributed,
+ cygwin1.dll has to be distributed as well. Since cygwin1.dll is under the GPL
+ licence, this forces not only PCRE to be under the GPL, but also the entire
+ application. A distributor who wants to keep their own code proprietary must
+ purchase an appropriate Cygwin licence.
+ MinGW has no such restrictions. The MinGW compiler generates a library or
+ executable that can run standalone on Windows without any third party dll or
+ licensing issues.
+ But there is more complication:
+ If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
+ to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a
+ front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's
+ gcc and MinGW's gcc). So, a user can:
+ . Build native binaries by using MinGW or by getting Cygwin and using
+   -mno-cygwin.
+ . Build binaries that depend on cygwin1.dll by using Cygwin with the normal
+   compiler flags.
+ The test files that are supplied with PCRE are in Unix format, with LF
+ characters as line terminators. It may be necessary to change the line
+ terminators in order to get some of the tests to work.
+ BUILDING PCRE ON WINDOWS WITH CMAKE
+ CMake is an alternative configuration facility that can be used instead of the
+ traditional Unix "configure". CMake creates project files (make files, solution
+ files, etc.) tailored to numerous development environments, including Visual
+ Studio, Borland, Msys, MinGW, NMake, and Unix. The following instructions
+ were contributed by a PCRE user.
+.  Install the latest CMake version available from http://www.cmake.org/, and
+     ensure that cmake\bin is on your path.
+.  Unzip (retaining folder structure) the PCRE source tree into a source
+     directory such as C:\pcre.
+.  Create a new, empty build directory, for example C:\pcre\build\
+.  Run cmake-gui from the Shell envirornment of your build tool, for example,
+     Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++.
+.  Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build
+     directories, respectively.
+.  Hit the "Configure" button.
+.  Select the particular IDE / build tool that you are using (Visual
+     Studio, MSYS makefiles, MinGW makefiles, etc.)
+.  The GUI will then list several configuration options. This is where
+     you can enable UTF-8 support or other PCRE optional features.
+.  Hit "Configure" again. The adjacent "Generate" button should now be
+     active.
+. Hit "Generate".
+. The build directory should now contain a usable build system, be it a
+     solution file for Visual Studio, makefiles for MinGW, etc. Exit from
+     cmake-gui and use the generated build system with your compiler or IDE.
+ USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
+ A PCRE user comments as follows:
+ I thought that others may want to know the current state of
+ CMAKE_USE_RELATIVE_PATHS support on Windows.
+ Here it is:
+ -- AdditionalIncludeDirectories is only partially modified (only the
+ first path - see below)
+ -- Only some of the contained file paths are modified - shown below for
+ pcre.vcproj
+ -- It properly modifies
+ I am sure CMake people can fix that if they want to. Until then one will
+ need to replace existing absolute paths in project files with relative
+ paths manually (e.g. from VS) - relative to project file location. I did
+ just that before being told to try CMAKE_USE_RELATIVE_PATHS. Not a big
+ deal.
+ AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7.5;"
+ AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;"
+ RelativePath="pcre.h">
+ RelativePath="pcre_chartables.c">
+ RelativePath="pcre_chartables.c.rule">
+ TESTING WITH RUNTEST.BAT
+. Copy RunTest.bat into the directory where pcretest.exe has been created.
+. Edit RunTest.bat and insert a line that indentifies the relative location of
+    the pcre source, e.g.:
+    set srcdir=..\pcre-7.4-RC3
+. Run RunTest.bat from a command shell environment. Test outputs will
+    automatically be compared to expected results, and discrepancies will
+    identified in the console output.
+. To test pcrecpp, run pcrecpp_unittest.exe, pcre_stringpiece_unittest.exe and
+    pcre_scanner_unittest.exe.
  BUILDING UNDER WINDOWS WITH BCC5.5
-Line 110 
 Michael Roy sent these comments about bu
+Line 398 
 Michael Roy sent these comments about bu
    line.
- OUT-OF-DATE COMMENTS ABOUT WIN32 BUILDS
+ BUILDING UNDER WINDOWS CE WITH VISUAL STUDIO 200x
- [These comments need looking at by someone who knows about Windows.]
+ Vincent Richomme sent a zip archive of files to help with this process. They
+ can be found in the file "pcre-vsbuild.zip" in the Contrib directory of the FTP
- Some help in building a Win32 DLL of PCRE in GnuWin32 environments was
+ site.
- contributed by Paul Sokolovsky. These environments are Mingw32
- (http://www.xraylith.wisc.edu/~khan/software/gnu-win32/) and CygWin
- (http://sourceware.cygnus.com/cygwin/). Paul comments:
-   For CygWin, set CFLAGS=-mno-cygwin, and do 'make dll'. You'll get
-   pcre.dll (containing pcreposix also), libpcre.dll.a, and dynamically
-   linked pgrep and pcretest. If you have /bin/sh, run RunTest (three
-   main test go ok, locale not supported).
- Changes to do MinGW with autoconf 2.50 were supplied by Fred Cox
- <sailorFred@yahoo.com>, who comments as follows:
-   If you are using the PCRE DLL, the normal Unix style configure && make &&
-   make check && make install should just work[*]. If you want to statically
-   link against the .a file, you must define PCRE_STATIC before including
-   pcre.h, otherwise the pcre_malloc and pcre_free exported functions will be
-   declared __declspec(dllimport), with hilarious results.  See the configure.in
-   and pcretest.c for how it is done for the static test.
-   Also, there will only be a libpcre.la, not a libpcreposix.la, as you
-   would expect from the Unix version. The single DLL includes the pcreposix
-   interface.
- [*] But note that the supplied test files are in Unix format, with just LF
- characters as line terminators. You will have to edit them to change to CR LF
- terminators.
- A script for building PCRE using Borland's C++ compiler for use with VPASCAL
- was contributed by Alexander Tokarev. It is called makevp.bat.
- These are some further comments about Win32 builds from Mark Evans. They
- were contributed before Fred Cox's changes were made, so it is possible that
- they may no longer be relevant.
- "The documentation for Win32 builds is a bit shy.  Under MSVC6 I
- followed their instructions to the letter, but there were still
- some things missing.
- (1) Must #define STATIC for entire project if linking statically.
-     (I see no reason to use DLLs for code this compact.)  This of
-     course is a project setting in MSVC under Preprocessor.
- (2) Missing some #ifdefs relating to the function pointers
-     pcre_malloc and pcre_free.  See my solution below.  (The stubs
-     may not be mandatory but they made me feel better.)"
- =========================
- #ifdef _WIN32
- #include <malloc.h>
- void* malloc_stub(size_t N)
- { return malloc(N); }
- void free_stub(void* p)
- { free(p); }
- void *(*pcre_malloc)(size_t) = &malloc_stub;
- void  (*pcre_free)(void *) = &free_stub;
- #else
- void *(*pcre_malloc)(size_t) = malloc;
- void  (*pcre_free)(void *) = free;
- #endif
- =========================
  BUILDING PCRE ON OPENVMS
-Line 245 
 $!   Locale could not be set to fr
+Line 469 
 $!   Locale could not be set to fr
  $!
  =========================
+ BUILDING PCRE ON STRATUS OPENVOS
+ These notes on the port of PCRE to VOS (lightly edited) were supplied by
+ Ashutosh Warikoo, whose email address has the local part awarikoo and the
+ domain nse.co.in. The port was for version 7.9 in August 2009.
+.   Building PCRE
+ I built pcre on OpenVOS Release 17.0.1at using GNU Tools 3.4a without any
+ problems. I used the following packages to build PCRE:
+   ftp://ftp.stratus.com/pub/vos/posix/ga/posix.save.evf.gz
+ Please read and follow the instructions that come with these packages. To start
+ the build of pcre, from the root of the package type:
+   ./build.sh
+. Installing PCRE
+ Once you have successfully built PCRE, login to the SysAdmin group, switch to
+ the root user, and type
+   [ !create_dir (master_disk)>usr   --if needed ]
+   [ !create_dir (master_disk)>usr>local   --if needed ]
+     !gmake install
+ This installs PCRE and its man pages into /usr/local. You can add
+ (master_disk)>usr>local>bin to your command search paths, or if you are in
+ BASH, add /usr/local/bin to the PATH environment variable.
+. Restrictions
+ This port requires readline library optionally. However during the build I
+ faced some yet unexplored errors while linking with readline. As it was an
+ optional component I chose to disable it.
+. Known Problems
+ I ran a the test suite, but you will have to be your own judge of whether this
+ command, and this port, suits your purposes. If you find any problems that
+ appear to be related to the port itself, please let me know. Please see the
+ build.log file in the root of the package also.
+ =========================
+ Last Updated: 23 August 2011
  ****

 Legend:



Removed from v.122
 


changed lines


 
Added in v.672
 Legend:



Removed from v.122
 


changed lines


 
Added in v.672
-Removed from v.122
+Added in v.672

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12