You read my mind Michael. When I run Xcodebuild on the project and then look at the arguments passed for the compile of the failing file, there is never a "-I /user/include" switch in the command line. In Windows I'd be setting it in either the INCLUDE environment variable, or setting the include directories in Visual Studio for either the project or the file. I've got 40 years in the industry so looking at a bunch of output from a build is nothing new for me.
Thanks for the help, but right now I do not believe this is a CMake issue. Gary Little H (952) 223-1349 C (952) 454-4629 gglit...@comcast.net On Apr 17, 2012, at 4:00 PM, Michael Jackson wrote: > You may want to take a very detailed look at the command line arguments that > Xcode is passing to the compiler. There you can pick apart all the include > paths that are being passed to the compiler and you will probably find that > /usr/include/boost is missing. Why it is missing is still unknown but at > least you would know that the CMake generated Xcode project is flawed. > -- > Mike Jackson <www.bluequartz.net> > > On Apr 17, 2012, at 4:47 PM, Gary Little wrote: > >> After beating my head against this brick wall for over a week I'm becoming >> convinced that the problem is neither with CMake nor with Boost. If I build >> the project as a Unix project or as a Visual Studio/nmake project, the >> created projects build fine whether it is for Linux, Darwin, or Windows. >> However, if I use CMake to build an Xcode project, then Xcode can NEVER find >> the boost header files that are located at "/usr/include/boost/...". The >> real kick in the head is if I use Xcode's project editing capabilities to >> add "/usr/include" to HEADER_SEARCH_PATHS it still cannot find the header >> files. If I then edit my header file from "<boost/random/uniform_int.hpp>" >> to "</usr/include/boost/random/uniform_int.hpp" it then finds the header >> file but then fails because that header include another file using >> "<boost/...". >> >> I dunno … I guess I was expecting Xcode to work as well as Visual Studio. It >> doesn't. >> >> Gary Little >> H (952) 223-1349 >> C (952) 454-4629 >> gglit...@comcast.net >> >> >> On Apr 12, 2012, at 12:34 PM, Gary Little wrote: >> >>> I've been porting a disk diagnostic tool we develop and use internally to >>> the Mac platform specified in the Subject. I have it to the point where >>> using CMake 2.8.7 it would create the plethora of sub-project builds, build >>> and link all of the dylibs that are used by Wish to run the diagnostics on >>> the drives that we manufacture. Recently however, I realized I needed a >>> better IDE than "vim", so I tried to run CMake to use Xcode 4.3.2. The >>> first thing that happened was a CMake error which should be solved in CMake >>> 2.8.8 RC1. It was, and CMake created the plethora of projects as well as >>> the single xcodeproj file that ties them all together. >>> >>> The project loads in Xcode, and does the builds, with quite a few warnings. >>> The warnings are nothing new, and like many shops we tend to ignore them … >>> not my choice since I'm a bit anal about fixing warnings, but I have to >>> live with these. However, I am not generating any dylibs, and when I go to >>> a terminal and run "xcodebuild -project MyP.xcodeproj" I find that the >>> build is actually failing with an error -- a Boost header file is not found. >>> >>> The path for the Boost headers are defined in the first CMakeLists.txt for >>> non Windows platforms as: include_directories("/usr/include"). An >>> additional include_directores adds the remaining paths and those are >>> defined. >>> >>> I've listed the files in that path and show boost defined under include >>> followed by all the header files that Xcode cannot find. My next thought >>> was to go look at HEADER_SEARCH_PATHS, and sure enough "/usr/include" is >>> not listed in that search path. I tried setting include_directores the >>> CMakeLists.txt file governs the actual project that is being built but that >>> does not work either. So, how do I set the search paths to find the Boost >>> header files? >>> >>> Also … How do I change build types in 2.8.8 RC2? The >>> -DCMAKE_BUILD_TYPE=Release that I used to use is no longer accepted. it >>> fails with a label not used message. >>> >>> Do I need to file a bug report, or am I doing or not doing something? >>> >>> Gary Little >>> H (952) 223-1349 >>> C (952) 454-4629 >>> gglit...@comcast.net >>> >>> >>> -- >>> >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the CMake FAQ at: >>> http://www.cmake.org/Wiki/CMake_FAQ >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.cmake.org/mailman/listinfo/cmake >> >> -- >> >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Follow this link to subscribe/unsubscribe: >> http://www.cmake.org/mailman/listinfo/cmake > > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake