/[pcre]/code/branches/oldtrunk8/NON-UNIX-USE

Diff of /code/branches/oldtrunk8/NON-UNIX-USE

Parent Directory | Revision Log | View Patch Patch

-revision 359 by ph10,
Wed Jul  9 16:20:19 2008 UTC
+revision 535 by ph10,
Thu Jun  3 19:18:24 2010 UTC
 Line 12 
 This document contains the following sec
    Comments about Win32 builds
    Building PCRE on Windows with CMake
    Use of relative paths with CMake on Windows
-   Testing with runtest.bat
+   Testing with RunTest.bat
    Building under Windows with BCC5.5
    Building PCRE on OpenVMS
+   Building PCRE on Stratus OpenVOS
  GENERAL
-Line 23 
 I (Philip Hazel) have no experience of W
+Line 24 
 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 36 
 wrapper functions are a separate issue (
+Line 37 
 wrapper functions are a separate issue (
  The PCRE distribution includes a "configure" file for use by the Configure/Make
  build system, as found in many Unix-like environments. There is also support
- support for CMake, which some users prefer, in particular in Windows
+ support for CMake, which some users prefer, especially in Windows environments.
- environments. There are some instructions for CMake under Windows in the
+ There are some instructions for CMake under Windows in the section entitled
- 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
- build PCRE in Unix-like systems.
+ Unix-like systems.
  GENERIC INSTRUCTIONS FOR THE PCRE C LIBRARY
-Line 85 
 The following are generic comments about
+Line 86 
 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.
-Line 113 
 The following are generic comments about
+Line 112 
 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 128 
 The following are generic comments about
+Line 127 
 The following are generic comments about
       your system has static and shared libraries, you may have to do this once
       for each type.
-  (8) Similarly, compile pcreposix.c (remembering -DHAVE_CONFIG_H if necessary)
+  (8) Similarly, if you want to build the POSIX wrapper functions, ensure that
-      and link the result (on its own) as the pcreposix library.
+      you have the pcreposix.h file and then compile pcreposix.c (remembering
+      -DHAVE_CONFIG_H if necessary). Link the result (on its own) as the
+      pcreposix library.
   (9) Compile the test program pcretest.c (again, don't forget -DHAVE_CONFIG_H).
-      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
-      It also needs the pcre_printint.src source file, which it #includes.
+      the pcreposix wrapper functions unless you compile it with -DNOPOSIX. The
+      pcretest.c program also needs the pcre_printint.src source file, which it
+      #includes.
  (10) Run pcretest on the testinput files in the testdata directory, and check
       that the output matches the corresponding testoutput files. Note that the
-Line 185 
 significantly slower when this is done.
+Line 188 
 significantly slower when this is done.
  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,
+ a non-dll .a file, you must define PCRE_STATIC before including pcre.h or
- otherwise the pcre_malloc() and pcre_free() exported functions will be declared
+ pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will
- __declspec(dllimport), with unwanted results.
+ 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).
-Line 274 
 gcc and MinGW's gcc). So, a user can:
+Line 277 
 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 improve
+ terminators in order to get some of the tests to work.
- things in this area in future.
  BUILDING PCRE ON WINDOWS WITH CMAKE
- 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
- traditional Unix "configure". CMake version 2.4.7 supports Borland makefiles,
+ traditional Unix "configure". CMake creates project files (make files, solution
- MinGW makefiles, MSYS makefiles, NMake makefiles, UNIX makefiles, Visual Studio
+ files, etc.) tailored to numerous development environments, including Visual
-, Visual Studio 7, Visual Studio 8, and Watcom W8. The following instructions
+ Studio, Borland, Msys, MinGW, NMake, and Unix. The following instructions
  were contributed by a PCRE user.
-.  Download CMake 2.4.7 or above from http://www.cmake.org/, install and ensure
+.  Install the latest CMake version available from http://www.cmake.org/, and
-     that cmake\bin is on your path.
+     ensure that cmake\bin is on your path.
 .  Unzip (retaining folder structure) the PCRE source tree into a source
      directory such as C:\pcre.
-.  Create a new, empty build directory: C:\pcre\build\
+.  Create a new, empty build directory, for example C:\pcre\build\
-.  Run CMakeSetup from the Shell envirornment of your build tool, e.g., Msys
+.  Run cmake-gui from the Shell envirornment of your build tool, for example,
-     for Msys/MinGW or Visual Studio Command Prompt for VC/VC++
+     Msys 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
-     directories, respectively
+     directories, respectively.
 .  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
-     MSYS makefiles, MinGW makefiles, etc.)
+     Studio, 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
-     enable UTF-8 support, etc.
+     you can enable UTF-8 support or other PCRE optional features.
-.  Hit "Configure" again. The adjacent "OK" button should now be active.
+.  Hit "Configure" again. The adjacent "Generate" button should now be
+     active.
-. Hit "OK".
+. Hit "Generate".
 . The build directory should now contain a usable build system, be it a
-     solution file for Visual Studio, makefiles for MinGW, etc.
+     solution file for Visual Studio, makefiles for MinGW, etc. Exit from
+     cmake-gui and use the generated build system with your compiler or IDE.
  USE OF RELATIVE PATHS WITH CMAKE ON WINDOWS
-Line 375 
 Michael Roy sent these comments about bu
+Line 379 
 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 439 
 $!   Locale could not be set to fr
+Line 450 
 $!   Locale could not be set to fr
  $!
  =========================
- Last Updated: 09 July 2008
+ BUILDING PCRE ON STRATUS OPENVOS
+ These notes on the port of PCRE to VOS (lightly edited) were supplied by
+ Ashutosh Warikoo, whose email address has the local part awarikoo and the
+ domain nse.co.in. The port was for version 7.9 in August 2009.
+.   Building PCRE
+ I built pcre on OpenVOS Release 17.0.1at using GNU Tools 3.4a without any
+ problems. I used the following packages to build PCRE:
+   ftp://ftp.stratus.com/pub/vos/posix/ga/posix.save.evf.gz
+ Please read and follow the instructions that come with these packages. To start
+ the build of pcre, from the root of the package type:
+   ./build.sh
+. Installing PCRE
+ Once you have successfully built PCRE, login to the SysAdmin group, switch to
+ the root user, and type
+   [ !create_dir (master_disk)>usr   --if needed ]
+   [ !create_dir (master_disk)>usr>local   --if needed ]
+     !gmake install
+ This installs PCRE and its man pages into /usr/local. You can add
+ (master_disk)>usr>local>bin to your command search paths, or if you are in
+ BASH, add /usr/local/bin to the PATH environment variable.
+. Restrictions
+ This port requires readline library optionally. However during the build I
+ faced some yet unexplored errors while linking with readline. As it was an
+ optional component I chose to disable it.
+. Known Problems
+ I ran a the test suite, but you will have to be your own judge of whether this
+ command, and this port, suits your purposes. If you find any problems that
+ appear to be related to the port itself, please let me know. Please see the
+ build.log file in the root of the package also.
+ =========================
+ Last Updated: 26 May 2010
  ****

 Legend:



Removed from v.359
 


changed lines


 
Added in v.535
 Legend:



Removed from v.359
 


changed lines


 
Added in v.535
-Removed from v.359
+Added in v.535

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12