/[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 401 by ph10, Sat Mar 21 17:13:18 2009 UTC revision 535 by ph10, Thu Jun 3 19:18:24 2010 UTC
# Line 12  This document contains the following sec Line 12  This document contains the following sec
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
15    Testing with runtest.bat    Testing with RunTest.bat
16    Building under Windows with BCC5.5    Building under Windows with BCC5.5
17    Building PCRE on OpenVMS    Building PCRE on OpenVMS
18      Building PCRE on Stratus OpenVOS
19    
20    
21  GENERAL  GENERAL
# Line 23  I (Philip Hazel) have no experience of W Line 24  I (Philip Hazel) have no experience of W
24  libraries work. The items in the PCRE distribution and Makefile that relate to  libraries work. The items in the PCRE distribution and Makefile that relate to
25  anything other than Unix-like systems are untested by me.  anything other than Unix-like systems are untested by me.
26    
27  There are some other comments and files (including some documentation in CHM  There are some other comments and files (including some documentation in CHM
28  format) in the Contrib directory on the FTP site:  format) in the Contrib directory on the FTP site:
29    
30    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib    ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/Contrib
# Line 36  wrapper functions are a separate issue ( Line 37  wrapper functions are a separate issue (
37    
38  The PCRE distribution includes a "configure" file for use by the Configure/Make  The PCRE distribution includes a "configure" file for use by the Configure/Make
39  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
40  support for CMake, which some users prefer, in particular in Windows  support for CMake, which some users prefer, especially in Windows environments.
41  environments. There are some instructions for CMake under Windows in the  There are some instructions for CMake under Windows in the section entitled
42  section entitled "Building PCRE with CMake" below. CMake can also be used to  "Building PCRE with CMake" below. CMake can also be used to build PCRE in
43  build PCRE in Unix-like systems.  Unix-like systems.
44    
45    
46  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
# Line 126  The following are generic comments about Line 127  The following are generic comments about
127       your system has static and shared libraries, you may have to do this once       your system has static and shared libraries, you may have to do this once
128       for each type.       for each type.
129    
130   (8) Similarly, compile pcreposix.c (remembering -DHAVE_CONFIG_H if necessary)   (8) Similarly, if you want to build the POSIX wrapper functions, ensure that
131       and link the result (on its own) as the pcreposix library.       you have the pcreposix.h file and then compile pcreposix.c (remembering
132         -DHAVE_CONFIG_H if necessary). Link the result (on its own) as the
133         pcreposix library.
134    
135   (9) Compile the test program pcretest.c (again, don't forget -DHAVE_CONFIG_H).   (9) Compile the test program pcretest.c (again, don't forget -DHAVE_CONFIG_H).
136       This needs the functions in the pcre and pcreposix libraries when linking.       This needs the functions in the PCRE library when linking. It also needs
137       It also needs the pcre_printint.src source file, which it #includes.       the pcreposix wrapper functions unless you compile it with -DNOPOSIX. The
138         pcretest.c program also needs the pcre_printint.src source file, which it
139         #includes.
140    
141  (10) Run pcretest on the testinput files in the testdata directory, and check  (10) Run pcretest on the testinput files in the testdata directory, and check
142       that the output matches the corresponding testoutput files. Note that the       that the output matches the corresponding testoutput files. Note that the
# Line 183  significantly slower when this is done. Line 188  significantly slower when this is done.
188  LINKING PROGRAMS IN WINDOWS ENVIRONMENTS  LINKING PROGRAMS IN WINDOWS ENVIRONMENTS
189    
190  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
191  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 or
192  otherwise the pcre_malloc() and pcre_free() exported functions will be declared  pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will
193  __declspec(dllimport), with unwanted results.  be declared __declspec(dllimport), with unwanted results.
194    
195    
196  CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS  CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS
# Line 272  gcc and MinGW's gcc). So, a user can: Line 277  gcc and MinGW's gcc). So, a user can:
277    
278  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
279  characters as line terminators. It may be necessary to change the line  characters as line terminators. It may be necessary to change the line
280  terminators in order to get some of the tests to work. We hope to improve  terminators in order to get some of the tests to work.
 things in this area in future.  
281    
282    
283  BUILDING PCRE ON WINDOWS WITH CMAKE  BUILDING PCRE ON WINDOWS WITH CMAKE
284    
285  CMake is an alternative build facility that can be used instead of the  CMake is an alternative configuration facility that can be used instead of the
286  traditional Unix "configure". CMake version 2.4.7 supports Borland makefiles,  traditional Unix "configure". CMake creates project files (make files, solution
287  MinGW makefiles, MSYS makefiles, NMake makefiles, UNIX makefiles, Visual Studio  files, etc.) tailored to numerous development environments, including Visual
288  6, Visual Studio 7, Visual Studio 8, and Watcom W8. The following instructions  Studio, Borland, Msys, MinGW, NMake, and Unix. The following instructions
289  were contributed by a PCRE user.  were contributed by a PCRE user.
290    
291  1.  Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure  1.  Install the latest CMake version available from http://www.cmake.org/, and
292      that cmake\bin is on your path.      ensure that cmake\bin is on your path.
293    
294  2.  Unzip (retaining folder structure) the PCRE source tree into a source  2.  Unzip (retaining folder structure) the PCRE source tree into a source
295      directory such as C:\pcre.      directory such as C:\pcre.
296    
297  3.  Create a new, empty build directory: C:\pcre\build\  3.  Create a new, empty build directory, for example C:\pcre\build\
298    
299  4.  Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys  4.  Run cmake-gui from the Shell envirornment of your build tool, for example,
300      for Msys/MinGW or Visual Studio Command Prompt for VC/VC++      Msys for Msys/MinGW or Visual Studio Command Prompt for VC/VC++.
301    
302  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
303      directories, respectively      directories, respectively.
304    
305  6.  Hit the "Configure" button.  6.  Hit the "Configure" button.
306    
307  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
308      MSYS makefiles, MinGW makefiles, etc.)      Studio, MSYS makefiles, MinGW makefiles, etc.)
309    
310  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
311      enable UTF-8 support, etc.      you can enable UTF-8 support or other PCRE optional features.
312    
313  9.  Hit "Configure" again. The adjacent "OK" button should now be active.  9.  Hit "Configure" again. The adjacent "Generate" button should now be
314        active.
315    
316  10. Hit "OK".  10. Hit "Generate".
317    
318  11. The build directory should now contain a usable build system, be it a  11. The build directory should now contain a usable build system, be it a
319      solution file for Visual Studio, makefiles for MinGW, etc.      solution file for Visual Studio, makefiles for MinGW, etc. Exit from
320        cmake-gui and use the generated build system with your compiler or IDE.
321    
322    
323  USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS  USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
# Line 444  $!   Locale could not be set to fr Line 450  $!   Locale could not be set to fr
450  $!  $!
451  =========================  =========================
452    
453  Last Updated: 17 March 2009  
454    BUILDING PCRE ON STRATUS OPENVOS
455    
456    These notes on the port of PCRE to VOS (lightly edited) were supplied by
457    Ashutosh Warikoo, whose email address has the local part awarikoo and the
458    domain nse.co.in. The port was for version 7.9 in August 2009.
459    
460    1.   Building PCRE
461    
462    I built pcre on OpenVOS Release 17.0.1at using GNU Tools 3.4a without any
463    problems. I used the following packages to build PCRE:
464    
465      ftp://ftp.stratus.com/pub/vos/posix/ga/posix.save.evf.gz
466    
467    Please read and follow the instructions that come with these packages. To start
468    the build of pcre, from the root of the package type:
469    
470      ./build.sh
471    
472    2. Installing PCRE
473    
474    Once you have successfully built PCRE, login to the SysAdmin group, switch to
475    the root user, and type
476    
477      [ !create_dir (master_disk)>usr   --if needed ]
478      [ !create_dir (master_disk)>usr>local   --if needed ]
479        !gmake install
480    
481    This installs PCRE and its man pages into /usr/local. You can add
482    (master_disk)>usr>local>bin to your command search paths, or if you are in
483    BASH, add /usr/local/bin to the PATH environment variable.
484    
485    4. Restrictions
486    
487    This port requires readline library optionally. However during the build I
488    faced some yet unexplored errors while linking with readline. As it was an
489    optional component I chose to disable it.
490    
491    5. Known Problems
492    
493    I ran a the test suite, but you will have to be your own judge of whether this
494    command, and this port, suits your purposes. If you find any problems that
495    appear to be related to the port itself, please let me know. Please see the
496    build.log file in the root of the package also.
497    
498    
499    =========================
500    Last Updated: 26 May 2010
501  ****  ****

Legend:
Removed from v.401  
changed lines
  Added in v.535

  ViewVC Help
Powered by ViewVC 1.1.5