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

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

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

revision 128 by ph10, Tue Mar 20 11:46:50 2007 UTC revision 134 by ph10, Mon Mar 26 16:00:17 2007 UTC
# Line 1  Line 1 
1  Compiling PCRE on non-Unix systems  Compiling PCRE on non-Unix systems
2  ----------------------------------  ----------------------------------
3    
4    This document contains the following sections:
5    
6      General
7      Generic instructions for the PCRE C library
8      The C++ wrapper functions
9      Building for virtual Pascal
10      Comments about Win32 builds
11      Building under Windows with BCC5.5
12      Building PCRE on OpenVMS
13    
14    
15    GENERAL
16    
17  I (Philip Hazel) have no knowledge of Windows or VMS sytems and how their  I (Philip Hazel) have no knowledge of Windows or VMS sytems and how their
18  libraries work. The items in the PCRE distribution and Makefile that relate to  libraries work. The items in the PCRE distribution and Makefile that relate to
19  anything other than Unix-like systems are untested by me.  anything other than Unix-like systems are untested by me.
# Line 17  should compile successfully on any syste Line 30  should compile successfully on any syste
30  library. The C++ wrapper functions are a separate issue (see below).  library. The C++ wrapper functions are a separate issue (see below).
31    
32    
33  GENERIC INSTRUCTIONS FOR THE C LIBRARY  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
34    
35  The following are generic comments about building the PCRE C library "by hand".  The following are generic comments about building the PCRE C library "by hand".
36    
# Line 105  BUILDING FOR VIRTUAL PASCAL Line 118  BUILDING FOR VIRTUAL PASCAL
118  A script for building PCRE using Borland's C++ compiler for use with VPASCAL  A script for building PCRE using Borland's C++ compiler for use with VPASCAL
119  was contributed by Alexander Tokarev. Stefan Weber updated the script and added  was contributed by Alexander Tokarev. Stefan Weber updated the script and added
120  additional files. The following files in the distribution are for building PCRE  additional files. The following files in the distribution are for building PCRE
121  for use with VP/Borland: makevp-compile.txt, makevp-linklib.txt, makevp.bat,  for use with VP/Borland: makevp-c.txt, makevp-l.txt, makevp.bat, pcregexp.pas.
 pcregexp.pas.  
122    
123    
124  BUILDING UNDER WINDOWS WITH BCC5.5  COMMENTS ABOUT WIN32 BUILDS
125    
126  Michael Roy sent these comments about building PCRE under Windows with BCC5.5:  There are two ways of building PCRE on Windows systems: using MinGW or using
127    Cygwin. These are not at all the same thing, and are completely different from
128    each other.
129    
130    Some of the core BCC libraries have a version of PCRE from 1998 built in,  The MinGW home page (http://www.mingw.org/) says this:
   which can lead to pcre_exec() giving an erroneous PCRE_ERROR_NULL from a  
   version mismatch. I'm including an easy workaround below, if you'd like to  
   include it in the non-unix instructions:  
131    
132    When linking a project with BCC5.5, pcre.lib must be included before any of    MinGW: A collection of freely available and freely distributable Windows
133    the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command    specific header files and import libraries combined with GNU toolsets that
134    line.    allow one to produce native Windows programs that do not rely on any
135      3rd-party C runtime DLLs.
136    
137    The Cygwin home page (http://www.cygwin.com/) says this:
138    
139  OUT-OF-DATE COMMENTS ABOUT WIN32 BUILDS    Cygwin is a Linux-like environment for Windows. It consists of two parts:
140    
141  [These comments need looking at by someone who knows about Windows.]    . A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing
142        substantial Linux API functionality
143    
144  Some help in building a Win32 DLL of PCRE in GnuWin32 environments was    . A collection of tools which provide Linux look and feel.
 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.  
   
 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.)"  
145    
146  =========================    The Cygwin DLL currently works with all recent, commercially released x86 32
147  #ifdef _WIN32    bit and 64 bit versions of Windows, with the exception of Windows CE.
 #include <malloc.h>  
148    
149  void* malloc_stub(size_t N)  On both MinGW and Cygwin, PCRE should build correctly using:
 { return malloc(N); }  
 void free_stub(void* p)  
 { free(p); }  
 void *(*pcre_malloc)(size_t) = &malloc_stub;  
 void  (*pcre_free)(void *) = &free_stub;  
150    
151  #else    ./configure && make && make install
152    
153  void *(*pcre_malloc)(size_t) = malloc;  However, if you want to statically link your program against the .a file, you
154  void  (*pcre_free)(void *) = free;  must define PCRE_STATIC before including pcre.h, otherwise the pcre_malloc()
155    and pcre_free() exported functions will be declared __declspec(dllimport), with
156    unwanted results.
157    
158  #endif  Using Cygwin's compiler generates libraries and executables that depend on
159  =========================  cygwin1.dll. If a library that is generated this way is distributed,
160    cygwin1.dll has to be distributed as well. Since cygwin1.dll is under the GPL
161    licence, this forces not only PCRE to be under the GPL, but also the entire
162    application. A distributor who wants to keep their own code proprietary must
163    purchase an appropriate Cygwin licence.
164    
165    MinGW has no such restrictions. The MinGW compiler generates a library or
166    executable that can run standalone on Windows without any third party dll or
167    licensing issues.
168    
169    But there is more complication:
170    
171    If a Cygwin user uses the -mno-cygwin Cygwin gcc flag, what that really does is
172    to tell Cygwin's gcc to use the MinGW gcc. Cygwin's gcc is only acting as a
173    front end to MinGW's gcc (if you install Cygwin's gcc, you get both Cygwin's
174    gcc and MinGW's gcc). So, a user can:
175    
176    . Build native binaries by using MinGW or by getting Cygwin and using
177      -mno-cygwin.
178    
179    . Build binaries that depend on cygwin1.dll by using Cygwin with the normal
180      compiler flags.
181    
182    The test files that are supplied with PCRE are in Unix format, with LF
183    characters as line terminators. It may be necessary to change the line
184    terminators in order to get some of the tests to work. We hope to improves
185    things in this area in future.
186    
187    
188    BUILDING UNDER WINDOWS WITH BCC5.5
189    
190    Michael Roy sent these comments about building PCRE under Windows with BCC5.5:
191    
192      Some of the core BCC libraries have a version of PCRE from 1998 built in,
193      which can lead to pcre_exec() giving an erroneous PCRE_ERROR_NULL from a
194      version mismatch. I'm including an easy workaround below, if you'd like to
195      include it in the non-unix instructions:
196    
197      When linking a project with BCC5.5, pcre.lib must be included before any of
198      the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command
199      line.
200    
201    
202  BUILDING PCRE ON OPENVMS  BUILDING PCRE ON OPENVMS
# Line 255  $! Locale could not be set to fr Line 263  $! Locale could not be set to fr
263  $!  $!
264  =========================  =========================
265    
266  Last Updated: 20 March 2007  Last Updated: 26 March 2007
267  ****  ****
Legend:
Removed from v.128  
changed lines
  Added in v.134
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12