diff options
author | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2008-01-21 15:22:09 +0000 |
---|---|---|
committer | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2008-01-21 15:22:09 +0000 |
commit | 9e0ca092ec1b8bf89370db008865fac757a046e9 (patch) | |
tree | d81937d6d890443ca1edbc60427193e9057f15f4 /NON-UNIX-USE | |
parent | 4ff532b445e64eb6453bccb24a8e23a6831488ea (diff) | |
download | pcre-9e0ca092ec1b8bf89370db008865fac757a046e9.tar.gz |
Tidies for 7.6-RC1 test release.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@309 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'NON-UNIX-USE')
-rw-r--r-- | NON-UNIX-USE | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/NON-UNIX-USE b/NON-UNIX-USE index e566e23..ff5b88e 100644 --- a/NON-UNIX-USE +++ b/NON-UNIX-USE @@ -295,7 +295,7 @@ were contributed by a PCRE user. 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. @@ -310,7 +310,7 @@ 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. +deal. AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7.5;" AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;" @@ -335,7 +335,7 @@ TESTING WITH RUNTEST.BAT 4. To test pcrecpp, run pcrecpp_unittest.exe, pcre_stringpiece_unittest.exe and pcre_scanner_unittest.exe. - + BUILDING UNDER WINDOWS WITH BCC5.5 |