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

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

Parent Directory | Revision Log | View Patch Patch

-revision 127 by ph10,
Mon Mar 19 11:44:45 2007 UTC
+revision 155 by ph10,
Tue Apr 24 13:36:11 2007 UTC
 Line 1
  Compiling PCRE on non-Unix systems
  ----------------------------------
+ This document contains the following sections:
+   General
+   Generic instructions for the PCRE C library
+   The C++ wrapper functions
+   Building for virtual Pascal
+   Comments about Win32 builds
+   Building under Windows with BCC5.5
+   Building PCRE on OpenVMS
+ GENERAL
  I (Philip Hazel) have no knowledge 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
- site that you may find useful, although a lot of them are now out-of-date. See
+ site that you may find useful. See
    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 contains some experimental support for "cmake", but this
+ is incomplete and not documented. However if you are a "cmake" user you might
+ like to try building with "cmake".
- GENERIC INSTRUCTIONS FOR THE C LIBRARY
+ GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
  The following are generic comments about building the PCRE C library "by hand".
-Line 31 
 The following are generic comments about
+Line 48 
 The following are generic comments about
  (2) Copy or rename the file pcre.h.generic as pcre.h.
- (3) Compile dftables.c as a stand-alone program, and then run it with
+ (3) EITHER:
-     the single argument "pcre_chartables.c". This generates a set of standard
+       Copy or rename file pcre_chartables.c.dist as pcre_chartables.c.
-     character tables and writes them to that file.
+     OR:
+       Compile dftables.c as a stand-alone program, and then run it with the
+       single argument "pcre_chartables.c". This generates a set of standard
+       character tables and writes them to that file. The tables are generated
+       using the default 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 command. You must use this method if you are building on
+       a system that uses EBCDIC code.
+     The tables in pcre_chartables.c are defaults. The caller of PCRE can
+     specify alternative tables at run time.
  (4) Compile the following source files:
-Line 91 
 xxx.cc files.
+Line 119 
 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: makevp-compile.txt, makevp-linklib.txt,
+ was contributed by Alexander Tokarev. Stefan Weber updated the script and added
- makevp.bat, 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.
- BUILDING UNDER WINDOWS WITH BCC5.5
+ COMMENTS ABOUT WIN32 BUILDS
- Michael Roy sent these comments about building PCRE under Windows with BCC5.5:
+ There are two ways of building PCRE using the "congifure, 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
+ some experimental, undocumented support for building using "cmake", which you
+ might like to try if you are familiar with "cmake". However, at the present
+ time, the "cmake" process builds only a static library (not a dll), and the
+ tests are not automatically run.
-   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:
-   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
-   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
-   line.
+   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:
- OUT-OF-DATE COMMENTS ABOUT WIN32 BUILDS
+   Cygwin is a Linux-like environment for Windows. It consists of two parts:
- [These comments need looking at by someone who knows about Windows.]
+   . A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing
+     substantial Linux API functionality
- 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.
- A script for building PCRE using Borland's C++ compiler for use with VPASCAL
+   The Cygwin DLL currently works with all recent, commercially released x86 32
- was contributed by Alexander Tokarev. It is called makevp.bat.
+   bit and 64 bit versions of Windows, with the exception of Windows CE.
- These are some further comments about Win32 builds from Mark Evans. They
+ On both MinGW and Cygwin, PCRE should build correctly using:
- 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.)"
- =========================
+   ./configure && make && make install
- #ifdef _WIN32
- #include <malloc.h>
- void* malloc_stub(size_t N)
+ This should create two libraries called libpcre and libpcreposix, and, if you
- { return malloc(N); }
+ have enabled building the C++ wrapper, a third one called libpcrecpp.
- void free_stub(void* p)
- { free(p); }
- void *(*pcre_malloc)(size_t) = &malloc_stub;
- void  (*pcre_free)(void *) = &free_stub;
- #else
+ If you want to statically link your program against a non-dll .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
+ unwanted results.
- void *(*pcre_malloc)(size_t) = malloc;
+ Using Cygwin's compiler generates libraries and executables that depend on
- void  (*pcre_free)(void *) = free;
+ 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.
- #endif
+ 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. We hope to improve
+ things in this area in future.
+ BUILDING UNDER WINDOWS WITH BCC5.5
+ Michael Roy sent these comments about building PCRE under Windows with BCC5.5:
+   Some of the core BCC libraries have a version of PCRE from 1998 built in,
+   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:
+   When linking a project with BCC5.5, pcre.lib must be included before any of
+   the libraries cw32.lib, cw32i.lib, cw32mt.lib, and cw32mti.lib on the command
+   line.
  BUILDING PCRE ON OPENVMS
-Line 245 
 $!   Locale could not be set to fr
+Line 274 
 $!   Locale could not be set to fr
  $!
  =========================
+ Last Updated: 24 April 2007
  ****

 Legend:



Removed from v.127
 


changed lines


 
Added in v.155
 Legend:



Removed from v.127
 


changed lines


 
Added in v.155
-Removed from v.127
+Added in v.155

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12