/[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 135 by ph10, Thu Mar 29 09:09:33 2007 UTC revision 181 by ph10, Wed Jun 13 14:55:18 2007 UTC
# Line 23  site that you may find useful. See Line 23  site that you may find useful. See
23    
24    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
25    
26  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
27  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
28  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
29  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++
30  library. The C++ wrapper functions are a separate issue (see below).  wrapper functions are a separate issue (see below).
31    
32    The PCRE distribution contains some experimental support for "cmake", but this
33    is incomplete and not documented. However if you are a "cmake" user you might
34    like to try building with "cmake".
35    
36    
37  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
# Line 41  The following are generic comments about Line 45  The following are generic comments about
45    
46      An alternative approach is not to edit config.h, but to use -D on the      An alternative approach is not to edit config.h, but to use -D on the
47      compiler command line to make any changes that you need.      compiler command line to make any changes that you need.
48    
49        NOTE: There have been occasions when the way in which certain parameters in
50        config.h are used has changed between releases. (In the configure/make
51        world, this is handled automatically.) When upgrading to a new release, you
52        are strongly advised to review config.h.generic before re-using what you
53        had previously.
54    
55  (2) Copy or rename the file pcre.h.generic as pcre.h.  (2) Copy or rename the file pcre.h.generic as pcre.h.
56    
# Line 123  for use with VP/Borland: makevp_c.txt, m Line 133  for use with VP/Borland: makevp_c.txt, m
133    
134  COMMENTS ABOUT WIN32 BUILDS  COMMENTS ABOUT WIN32 BUILDS
135    
136  There are two ways of building PCRE on Windows systems: using MinGW or using  There are two ways of building PCRE using the "configure, make, make install"
137  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
138  each other.  the same thing; they are completely different from each other. There is also
139    some experimental, undocumented support for building using "cmake", which you
140    might like to try if you are familiar with "cmake". However, at the present
141    time, the "cmake" process builds only a static library (not a dll), and the
142    tests are not automatically run.
143    
144  The MinGW home page (http://www.mingw.org/) says this:  The MinGW home page (http://www.mingw.org/) says this:
145    
# Line 150  On both MinGW and Cygwin, PCRE should bu Line 164  On both MinGW and Cygwin, PCRE should bu
164    
165    ./configure && make && make install    ./configure && make && make install
166    
167  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
168  must define PCRE_STATIC before including pcre.h, otherwise the pcre_malloc()  have enabled building the C++ wrapper, a third one called libpcrecpp. These are
169  and pcre_free() exported functions will be declared __declspec(dllimport), with  independent libraries: when you like with libpcreposix or libpcrecpp you must
170    also link with libpcre, which contains the basic functions. (Some earlier
171    releases of PCRE included the basic libpcre functions in libpcreposix. This no
172    longer happens.)
173    
174    If you want to statically link your program against a non-dll .a file, you must
175    define PCRE_STATIC before including pcre.h, otherwise the pcre_malloc() and
176    pcre_free() exported functions will be declared __declspec(dllimport), with
177  unwanted results.  unwanted results.
178    
179  Using Cygwin's compiler generates libraries and executables that depend on  Using Cygwin's compiler generates libraries and executables that depend on
# Line 181  gcc and MinGW's gcc). So, a user can: Line 202  gcc and MinGW's gcc). So, a user can:
202    
203  The test files that are supplied with PCRE are in Unix format, with LF  The test files that are supplied with PCRE are in Unix format, with LF
204  characters as line terminators. It may be necessary to change the line  characters as line terminators. It may be necessary to change the line
205  terminators in order to get some of the tests to work. We hope to improves  terminators in order to get some of the tests to work. We hope to improve
206  things in this area in future.  things in this area in future.
207    
208    
# Line 263  $! Locale could not be set to fr Line 284  $! Locale could not be set to fr
284  $!  $!
285  =========================  =========================
286    
287  Last Updated: 26 March 2007  Last Updated: 13 June 2007
288  ****  ****

Legend:
Removed from v.135  
changed lines
  Added in v.181

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12