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

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

Parent Directory | Revision Log | View Patch Patch

-revision 260 by ph10,
Thu Sep 20 10:19:16 2007 UTC
+revision 401 by ph10,
Sat Mar 21 17:13:18 2009 UTC
 Line 8 
 This document contains the following sec
    The C++ wrapper functions
    Building for virtual Pascal
    Stack size in Windows environments
+   Linking programs in Windows environments
    Comments about Win32 builds
-   Building PCRE with CMake
+   Building PCRE on Windows with CMake
+   Use of relative paths with CMake on Windows
+   Testing with runtest.bat
    Building under Windows with BCC5.5
    Building PCRE on OpenVMS
-Line 20 
 I (Philip Hazel) have no experience of W
+Line 23 
 I (Philip Hazel) have no experience of W
  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
+ There are some other comments and files (including some documentation in CHM
- site that you may find useful. See
+ format) in the Contrib directory on the FTP site:
    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
-Line 31 
 library consists entirely of code writte
+Line 34 
 library consists entirely of code writte
  successfully on any system that has a Standard C compiler and library. The C++
  wrapper functions are a separate issue (see below).
- The PCRE distribution includes support for CMake. This support is relatively
+ The PCRE distribution includes a "configure" file for use by the Configure/Make
- new, but has already been used successfully to build PCRE in multiple build
+ build system, as found in many Unix-like environments. There is also support
- environments on Windows. There are some instructions in the section entitled
+ support for CMake, which some users prefer, in particular in Windows
- "Building PCRE with CMake" below.
+ environments. There are some instructions for CMake under Windows in the
+ section entitled "Building PCRE with CMake" below. CMake can also be used to
+ build PCRE in Unix-like systems.
  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
-Line 80 
 The following are generic comments about
+Line 85 
 The following are generic comments about
         pcre_internal.h
         ucp.h
-        ucpinternal.h
-        ucptable.h
   (5) Also ensure that you have the following file, which is #included as source
-      when building a debugging version of PCRE and is also used by pcretest.
+      when building a debugging version of PCRE, and is also used by pcretest.
         pcre_printint.src
-Line 108 
 The following are generic comments about
+Line 111 
 The following are generic comments about
         pcre_study.c
         pcre_tables.c
         pcre_try_flipped.c
-        pcre_ucp_searchfuncs.c
+        pcre_ucd.c
         pcre_valid_utf8.c
         pcre_version.c
         pcre_xclass.c
-Line 169 
 fail because of this. Normally, running
+Line 172 
 fail because of this. Normally, running
  have been cases where the test program has just died silently. See your linker
  documentation for how to increase stack size if you experience problems. The
  Linux default of 8Mb is a reasonable choice for the stack, though even that can
  be too small for some pattern/subject combinations.
  PCRE has a compile configuration option to disable the use of stack for
  recursion so that heap is used instead. However, pattern matching is
-Line 177 
 significantly slower when this is done.
+Line 180 
 significantly slower when this is done.
  "pcrestack" documentation.
+ LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
+ If you want to statically link a program against a PCRE library in the form of
+ 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.
+ CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS
+ It is possible to compile programs to use different calling conventions using
+ MSVC. Search the web for "calling conventions" for more information. To make it
+ easier to change the calling convention for the exported functions in the
+ PCRE library, the macro PCRE_CALL_CONVENTION is present in all the external
+ definitions. It can be set externally when compiling (e.g. in CFLAGS). If it is
+ not set, it defaults to empty; the default calling convention is then used
+ (which is what is wanted most of the time).
  COMMENTS ABOUT WIN32 BUILDS (see also "BUILDING PCRE WITH CMAKE" below)
  There are two ways of building PCRE using the "configure, 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
+ support for building using CMake, which some users find a more straightforward
- might like to try if you are familiar with "cmake". However, at the present
+ way of building PCRE under Windows. However, the tests are not run
- time, the "cmake" process builds only a static library (not a dll), and the
+ automatically when CMake is used.
- tests are not automatically run.
  The MinGW home page (http://www.mingw.org/) says this:
-Line 217 
 also link with libpcre, which contains t
+Line 238 
 also link with libpcre, which contains t
  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
+ A user submitted a special-purpose patch that makes it easy to create
- define PCRE_STATIC before including pcre.h, otherwise the pcre_malloc() and
+ "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"
- pcre_free() exported functions will be declared __declspec(dllimport), with
+ as a special target. If you use this target, no other files are built, and in
- unwanted results.
+ particular, the pcretest and pcregrep programs are not built. An example of how
+ this might be used is:
+   ./configure --enable-utf --disable-cpp CFLAGS="-03 -s"; make pcre.dll
  Using Cygwin's compiler generates libraries and executables that depend on
  cygwin1.dll. If a library that is generated this way is distributed,
-Line 252 
 terminators in order to get some of the
+Line 276 
 terminators in order to get some of the
  things in this area in future.
- BUILDING PCRE WITH CMAKE
+ BUILDING PCRE ON WINDOWS WITH CMAKE
  CMake is an alternative build facility that can be used instead of the
  traditional Unix "configure". CMake version 2.4.7 supports Borland makefiles,
-Line 260 
 MinGW makefiles, MSYS makefiles, NMake m
+Line 284 
 MinGW makefiles, MSYS makefiles, NMake m
 , Visual Studio 7, Visual Studio 8, and Watcom W8. The following instructions
  were contributed by a PCRE user.
-. Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure
+.  Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure
-    that cmake\bin is on your path.
+     that cmake\bin is on your path.
-. Unzip (retaining folder structure) the PCRE source tree into a source
+.  Unzip (retaining folder structure) the PCRE source tree into a source
-    directory such as C:\pcre.
+     directory such as C:\pcre.
-. Create a new, empty build directory: C:\pcre\build\
+.  Create a new, empty build directory: C:\pcre\build\
-. Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys
+.  Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys
-    for Msys/MinGW or Visual Studio Command Prompt for VC/VC++
+     for Msys/MinGW or Visual Studio Command Prompt for VC/VC++
-. Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build
+.  Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build
-    directories, respectively
+     directories, respectively
-. Hit the "Configure" button.
+.  Hit the "Configure" button.
-. Select the particular IDE / build tool that you are using (Visual Studio,
+.  Select the particular IDE / build tool that you are using (Visual Studio,
-    MSYS makefiles, MinGW makefiles, etc.)
+     MSYS makefiles, MinGW makefiles, etc.)
-. The GUI will then list several configuration options. This is where you can
+.  The GUI will then list several configuration options. This is where you can
-    enable UTF-8 support, etc.
+     enable UTF-8 support, etc.
-. Hit "Configure" again. The adjacent "OK" button should now be active.
+.  Hit "Configure" again. The adjacent "OK" button should now be active.
 . Hit "OK".
 . The build directory should now contain a usable build system, be it a
      solution file for Visual Studio, makefiles for MinGW, etc.
- Testing with RunTest.bat
+ USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
+ A PCRE user comments as follows:
+ I thought that others may want to know the current state of
+ CMAKE_USE_RELATIVE_PATHS support on Windows.
+ Here it is:
+ -- AdditionalIncludeDirectories is only partially modified (only the
+ first path - see below)
+ -- Only some of the contained file paths are modified - shown below for
+ pcre.vcproj
+ -- It properly modifies
+ I am sure CMake people can fix that if they want to. Until then one will
+ need to replace existing absolute paths in project files with relative
+ paths manually (e.g. from VS) - relative to project file location. I did
+ just that before being told to try CMAKE_USE_RELATIVE_PATHS. Not a big
+ deal.
+ AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7.5;"
+ AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;"
+ RelativePath="pcre.h">
+ RelativePath="pcre_chartables.c">
+ RelativePath="pcre_chartables.c.rule">
+ TESTING WITH RUNTEST.BAT
 . Copy RunTest.bat into the directory where pcretest.exe has been created.
-Line 320 
 Michael Roy sent these comments about bu
+Line 373 
 Michael Roy sent these comments about bu
    line.
+ BUILDING UNDER WINDOWS CE WITH VISUAL STUDIO 200x
+ Vincent Richomme sent a zip archive of files to help with this process. They
+ can be found in the file "pcre-vsbuild.zip" in the Contrib directory of the FTP
+ site.
  BUILDING PCRE ON OPENVMS
  Dan Mooney sent the following comments about building PCRE on OpenVMS. They
-Line 384 
 $!   Locale could not be set to fr
+Line 444 
 $!   Locale could not be set to fr
  $!
  =========================
- Last Updated: 21 September 2007
+ Last Updated: 17 March 2009
  ****

 Legend:



Removed from v.260
 


changed lines


 
Added in v.401
 Legend:



Removed from v.260
 


changed lines


 
Added in v.401
-Removed from v.260
+Added in v.401

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12