/[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 318 by ph10, Fri Jan 25 17:57:39 2008 UTC revision 319 by ph10, Mon Jan 28 15:27:45 2008 UTC
# Line 8  This document contains the following sec Line 8  This document contains the following sec
8    The C++ wrapper functions    The C++ wrapper functions
9    Building for virtual Pascal    Building for virtual Pascal
10    Stack size in Windows environments    Stack size in Windows environments
11    Linking programs in Windows environments    Linking programs in Windows environments
12    Comments about Win32 builds    Comments about Win32 builds
13    Building PCRE on Windows with CMake    Building PCRE on Windows with CMake
14    Use of relative paths with CMake on Windows    Use of relative paths with CMake on Windows
# Line 38  The PCRE distribution includes a "config Line 38  The PCRE distribution includes a "config
38  build system, as found in many Unix-like environments. There is also support  build system, as found in many Unix-like environments. There is also support
39  support for CMake, which some users prefer, in particular in Windows  support for CMake, which some users prefer, in particular in Windows
40  environments. There are some instructions for CMake under Windows in the  environments. There are some instructions for CMake under Windows in the
41  section entitled "Building PCRE with CMake" below. CMake can also be used to  section entitled "Building PCRE with CMake" below. CMake can also be used to
42  build PCRE in Unix-like systems.  build PCRE in Unix-like systems.
43    
44    
# Line 184  significantly slower when this is done. Line 184  significantly slower when this is done.
184    
185  LINKING PROGRAMS IN WINDOWS ENVIRONMENTS  LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
186    
187  If you want to statically link a program against a PCRE library in the form of  If you want to statically link a program against a PCRE library in the form of
188  a non-dll .a file, you must define PCRE_STATIC before including pcre.h,  a non-dll .a file, you must define PCRE_STATIC before including pcre.h,
189  otherwise the pcre_malloc() and pcre_free() exported functions will be declared  otherwise the pcre_malloc() and pcre_free() exported functions will be declared
190  __declspec(dllimport), with unwanted results.  __declspec(dllimport), with unwanted results.
# Line 195  COMMENTS ABOUT WIN32 BUILDS (see also "B Line 195  COMMENTS ABOUT WIN32 BUILDS (see also "B
195  There are two ways of building PCRE using the "configure, make, make install"  There are two ways of building PCRE using the "configure, make, make install"
196  paradigm on Windows systems: using MinGW or using Cygwin. These are not at all  paradigm on Windows systems: using MinGW or using Cygwin. These are not at all
197  the same thing; they are completely different from each other. There is also  the same thing; they are completely different from each other. There is also
198  support for building using CMake, which some users find a more straightforward  support for building using CMake, which some users find a more straightforward
199  way of building PCRE under Windows. However, the tests are not run  way of building PCRE under Windows. However, the tests are not run
200  automatically when CMake is used.  automatically when CMake is used.
201    
202  The MinGW home page (http://www.mingw.org/) says this:  The MinGW home page (http://www.mingw.org/) says this:
# Line 230  releases of PCRE included the basic libp Line 230  releases of PCRE included the basic libp
230  longer happens.)  longer happens.)
231    
232  A user submitted a special-purpose patch that makes it easy to create  A user submitted a special-purpose patch that makes it easy to create
233  "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"  "pcre.dll" under mingw32 using the "msys" environment. It provides "pcre.dll"
234  as a special target. If you use this target, no other files are built, and in  as a special target. If you use this target, no other files are built, and in
235  particular, the pcretest and pcregrep programs are not built. An example of how  particular, the pcretest and pcregrep programs are not built. An example of how
236  this might be used is:  this might be used is:
# Line 277  were contributed by a PCRE user. Line 277  were contributed by a PCRE user.
277    
278  1.  Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure  1.  Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure
279      that cmake\bin is on your path.      that cmake\bin is on your path.
280    
281  2.  Unzip (retaining folder structure) the PCRE source tree into a source  2.  Unzip (retaining folder structure) the PCRE source tree into a source
282      directory such as C:\pcre.      directory such as C:\pcre.
283    
284  3.  Create a new, empty build directory: C:\pcre\build\  3.  Create a new, empty build directory: C:\pcre\build\
285    
286  4.  Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys  4.  Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys
287      for Msys/MinGW or Visual Studio Command Prompt for VC/VC++      for Msys/MinGW or Visual Studio Command Prompt for VC/VC++
288    
289  5.  Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build  5.  Enter C:\pcre\pcre-xx and C:\pcre\build for the source and build
290      directories, respectively      directories, respectively
291    
292  6.  Hit the "Configure" button.  6.  Hit the "Configure" button.
293    
294  7.  Select the particular IDE / build tool that you are using (Visual Studio,  7.  Select the particular IDE / build tool that you are using (Visual Studio,
295      MSYS makefiles, MinGW makefiles, etc.)      MSYS makefiles, MinGW makefiles, etc.)
296    
297  8.  The GUI will then list several configuration options. This is where you can  8.  The GUI will then list several configuration options. This is where you can
298      enable UTF-8 support, etc.      enable UTF-8 support, etc.
299    
300  9.  Hit "Configure" again. The adjacent "OK" button should now be active.  9.  Hit "Configure" again. The adjacent "OK" button should now be active.
301    
302  10. Hit "OK".  10. Hit "OK".
Legend:
Removed from v.318  
changed lines
  Added in v.319
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12