summaryrefslogtreecommitdiff
path: root/NON-UNIX-USE
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-04-04 14:06:52 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2007-04-04 14:06:52 +0000
commit765b484a8ea8410faa15130c965d56b81eff29d6 (patch)
tree5c81c25f181ff13a5e1016cd9d967df2fd14e42b /NON-UNIX-USE
parent538ef4f8d6632b422169714282844c34b4bfc271 (diff)
downloadpcre-765b484a8ea8410faa15130c965d56b81eff29d6.tar.gz
Reworked all the WIN32 __declspec stuff in the hope of getting it right.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@145 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'NON-UNIX-USE')
-rw-r--r--NON-UNIX-USE12
1 files changed, 6 insertions, 6 deletions
diff --git a/NON-UNIX-USE b/NON-UNIX-USE
index 2b82b7c..e2009ac 100644
--- a/NON-UNIX-USE
+++ b/NON-UNIX-USE
@@ -29,8 +29,8 @@ library consists entirely of code written in Standard C, and so should compile
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 contains some experimental support for "cmake", but this
-is incomplete and not documented. However if you are a "cmake" user you might
+The PCRE distribution contains some experimental support for "cmake", but this
+is incomplete and not documented. However if you are a "cmake" user you might
like to try building with "cmake".
@@ -127,11 +127,11 @@ for use with VP/Borland: makevp_c.txt, makevp_l.txt, makevp.bat, pcregexp.pas.
COMMENTS ABOUT WIN32 BUILDS
-There are two ways of building PCRE using the "congifure, make, make install"
+There are two ways of building PCRE using the "congifure, 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
-might like to try if you are familiar with "cmake". However, at the present
+the same thing; they are completely different from each other. There is also
+some experimental, undocumented support for building using "cmake", which you
+might like to try if you are familiar with "cmake". However, at the present
time, the "cmake" process builds only a static library (not a dll), and the
tests are not automatically run.