Re: [Mingw-cross-env-list] cmake unable to find boost_thread

[Brad Pitcher]

Good call! All I had to do was set _boost_COMPILER to "_win32" and add the following pattern to the checked patterns:
${Boost_LIB_PREFIX}boost_${COMPONENT}${_boost_COMPILER}${_boost_MULTITHREADED}

Now I have another issue to debug:
[ 33%] Building CXX object src/CGAL/CMakeFiles/CGAL.dir/all_files.cpp.obj
In file included from /home/brad/Downloads/CGAL-3.8/src/CGAL/assertions.cpp:24:0,
                 from /home/brad/Downloads/CGAL-3.8/src/CGAL/all_files.cpp:20:
/home/brad/Downloads/CGAL-3.8/include/CGAL/config.h:66:4: error: #error "This compiler does not have a working STL"
make[2]: *** [src/CGAL/CMakeFiles/CGAL.dir/all_files.cpp.obj] Error 1
make[1]: *** [src/CGAL/CMakeFiles/CGAL.dir/all] Error 2
make: *** [all] Error 2

Fortunately, a web search reveals a plethora of other folks with the issue although I'd doubt if any of them are using mingw-cross-env. I will begin to wade through the results, but if you've seen this before or have any ideas, please speak up.
Thanks,
Brad

I'm shocked, I actually got this beast to compile. It turned out to be 
because of something cmake was doing:

CMake Error: TRY_RUN() invoked in cross-compiling mode, please set the 
following cache variables appropriatly:
   CGAL_CFG_NO_STL (advanced)
   CGAL_CFG_NO_STL__TRYRUN_OUTPUT (advanced)
For details see /home/brad/Downloads/CGAL-3.8/TryRunResults.cmake
-- Performing Test CGAL_CFG_NO_STL - Failed

It would still make a makefile, but failed on build with the STL error I
 posted before. I followed the advice here 
(http://www.cmake.org/Wiki/BuildingPythonWithCMake) and edited the 
TryRunResults.cmake file. I used "0" for both CGAL_CFG_NO_STL and 
CGAL_CFG_NO_STL__TRYRUN_OUTPUT and saved the file to 
cmake/TryRunResults.mingw-cross-env.cmake. Then I deleted CMakeCache.txt
 and ran:

cmake 
-DCMAKE_TOOLCHAIN_FILE=/opt/mingw/usr/i686-pc-mingw32/share/cmake/mingw-cross-env-conf.cmake
 -C cmake/TryRunResults.mingw-cross-env.cmake .

It actually makes some beautiful .a files, now I just need to see if I 
can use them.
I'm curious though, is there a better way around this? Can't we 
configure wine to run these tests or something?
Cheers,
Brad