Philip Hazel schrieb:
> On Mon, 21 Jan 2008, Sheri wrote:
>
>> Currently doesn't build (configured with cmake)
>
> Oh dear. I did test the revised CMake config on Linux...
>
> Christian, are you reading this?
>
>> [ 15%] Building C object CMakeFiles/pcre.dir/pcre_config.obj
>> /C/MinGW/bin/gcc.exe -Dpcre_EXPORTS -O3 -DNDEBUG
>> -I/C/pcre-7.6/cmake-msys-sha
>> red-RC1 -I/C/pcre-7.6/pcre-7.6-RC1 -DHAVE_CONFIG_H -o
>> CMakeFiles/pcre.dir/pcre
>> _config.obj -c /C/pcre-7.6/pcre-7.6-RC1/pcre_config.c
>> c:/pcre-7.6/pcre-7.6-RC1/pcre_config.c: In function `pcre_config':
>> c:/pcre-7.6/pcre-7.6-RC1/pcre_config.c:103: error: `ON' undeclared
>
> Line 103 of pcre_config.c reads
>
> *((int *)where) = POSIX_MALLOC_THRESHOLD;
>
>> This shows my cmake configuration summary. I configured with cmake build
>> type of "Release", maybe that should also show up on this list.
>> Everything except the readline output is consistent with my cmakesetup
>> choices. I did put in readline include location and readline library (in
>> cmakesetup).
>>
>> -- PCRE configuration summary:
>> --
>> -- Install prefix .................. : C:/Program Files/PCRE
>> -- C compiler ...................... : C:/MinGW/bin/gcc.exe
>> -- C++ compiler .................... : c:/mingw/bin/g++.exe
>> -- C compiler flags ................ :
>> -- C++ compiler flags .............. :
>> --
>> -- Build C++ library ............... : ON
>> -- Enable UTF-8 support ............ : ON
>> -- Unicode properties .............. : ON
>> -- Newline char/sequence ........... : ANYCRLF
>> -- \R matches only ANYCRLF ......... : ON
>> -- EBCDIC coding ................... : OFF
>> -- Rebuild char tables ............. : ON
>> -- Use stack recursion ............. : OFF
>> -- POSIX mem threshold ............. : ON
> ^^
> ^^
> ^^
> There's the problem. The value should be a number. The default is 10 if
> I recall correctly, and that's what I got when I ran cmake on Linux.
>
And that's also what I get on windows - and the cmake script doesn't say
anything else. The only thing which could be is that you're using an old
CMakeCache.txt (i.e. not a clean build dir) or changed this value by
accident with CMakeSetup.
The script doesn't do anything with the value. It's only set to 10 and
later printed.
Christian