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

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

Parent Directory | 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
    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 41 
 The following are generic comments about
+Line 45 
 The following are generic comments about
      An alternative approach is not to edit config.h, but to use -D on the
      compiler command line to make any changes that you need.
+     NOTE: There have been occasions when the way in which certain parameters in
+     config.h are used has changed between releases. (In the configure/make
+     world, this is handled automatically.) When upgrading to a new release, you
+     are strongly advised to review config.h.generic before re-using what you
+     had previously.
  (2) Copy or rename the file pcre.h.generic as pcre.h.
-Line 123 
 for use with VP/Borland: makevp_c.txt, m
+Line 133 
 for use with VP/Borland: makevp_c.txt, m
  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 "configure, 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 150 
 On both MinGW and Cygwin, PCRE should bu
+Line 164 
 On both MinGW and Cygwin, PCRE should bu
    ./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. These are
- and pcre_free() exported functions will be declared __declspec(dllimport), with
+ independent libraries: when you like 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.)
+ 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 181 
 gcc and MinGW's gcc). So, a user can:
+Line 202 
 gcc and MinGW's gcc). So, a user can:
  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
+ terminators in order to get some of the tests to work. We hope to improve
  things in this area in future.
-Line 263 
 $!   Locale could not be set to fr
+Line 284 
 $!   Locale could not be set to fr
  $!
  =========================
- Last Updated: 26 March 2007
+ Last Updated: 13 June 2007
  ****

 Legend:



Removed from v.135
 


changed lines


 
Added in v.181
 Legend:



Removed from v.135
 


changed lines


 
Added in v.181
-Removed from v.135
+Added in v.181

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12