diff options
| -rw-r--r-- | NON-UNIX-USE | 8 | ||||
| -rw-r--r-- | doc/pcreapi.3 | 4 |
2 files changed, 6 insertions, 6 deletions
diff --git a/NON-UNIX-USE b/NON-UNIX-USE index 69668cb..d4f0591 100644 --- a/NON-UNIX-USE +++ b/NON-UNIX-USE @@ -188,9 +188,9 @@ significantly slower when this is done. There is more about stack usage in the 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, -otherwise the pcre_malloc() and pcre_free() exported functions will be declared -__declspec(dllimport), with unwanted results. +a non-dll .a file, you must define PCRE_STATIC before including pcre.h or +pcrecpp.h, otherwise the pcre_malloc() and pcre_free() exported functions will +be declared __declspec(dllimport), with unwanted results. CALLING CONVENTIONS IN WINDOWS ENVIRONMENTS @@ -497,5 +497,5 @@ build.log file in the root of the package also. ========================= -Last Updated: 19 January 2010 +Last Updated: 26 May 2010 **** diff --git a/doc/pcreapi.3 b/doc/pcreapi.3 index 467f7d4..b53e7a9 100644 --- a/doc/pcreapi.3 +++ b/doc/pcreapi.3 @@ -134,8 +134,8 @@ Applications can use these to include support for different releases of PCRE. .P In a Windows environment, if you want to statically link an application program against a non-dll \fBpcre.a\fP file, you must define PCRE_STATIC before -including \fBpcre.h\fP, because otherwise the \fBpcre_malloc()\fP and -\fBpcre_free()\fP exported functions will be declared +including \fBpcre.h\fP or \fBpcrecpp.h\fP, because otherwise the +\fBpcre_malloc()\fP and \fBpcre_free()\fP exported functions will be declared \fB__declspec(dllimport)\fP, with unwanted results. .P The functions \fBpcre_compile()\fP, \fBpcre_compile2()\fP, \fBpcre_study()\fP, |