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

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

Parent Directory | Revision Log | View Patch Patch

-revision 131 by ph10,
Mon Mar 26 15:10:12 2007 UTC
+revision 148 by ph10,
Mon Apr 16 13:25:10 2007 UTC
 Line 4 
 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
 Line 23 
 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 PCRE C LIBRARY
-Line 118 
 BUILDING FOR VIRTUAL PASCAL
+Line 122 
 BUILDING FOR VIRTUAL PASCAL
  A script for building PCRE using Borland's C++ compiler for use with VPASCAL
  was contributed by Alexander Tokarev. Stefan Weber updated the script and added
  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.
+ for use with VP/Borland: makevp_c.txt, makevp_l.txt, makevp.bat, pcregexp.pas.
  COMMENTS ABOUT WIN32 BUILDS
- There are two ways of building PCRE on Windows systems: using MinGW or using
+ There are two ways of building PCRE using the "congifure, make, make install"
- Cygwin. These are not at all the same thing, and are completely different from
+ paradigm on Windows systems: using MinGW or using Cygwin. These are not at all
- each other.
+ 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.
  The MinGW home page (http://www.mingw.org/) says this:
-Line 136 
 The MinGW home page (http://www.mingw.or
+Line 144 
 The MinGW home page (http://www.mingw.or
  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
- However, if you want to statically link your program against the .a file, you
+ This should create two libraries called libpcre and libpcreposix, and, if you
- must define PCRE_STATIC before including pcre.h, otherwise the pcre_malloc()
+ have enabled building the C++ wrapper, a third one called libpcrecpp.
- and pcre_free() exported functions will be declared __declspec(dllimport), with
+ 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.
  Using Cygwin's compiler generates libraries and executables that depend on
-Line 173 
 to tell Cygwin's gcc to use the MinGW gc
+Line 184 
 to tell Cygwin's gcc to use the MinGW gc
  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 improves
  things in this area in future.

 Legend:



Removed from v.131
 


changed lines


 
Added in v.148
 Legend:



Removed from v.131
 


changed lines


 
Added in v.148
-Removed from v.131
+Added in v.148

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12