From: gbiggs <gb...@ki...> - 2008-06-18 02:18:45
|
Brian Gerkey wrote: > Yeah, on OS X (at least on my machine), I only have a libboost_thread- > mt, no libboost_thread. I've run into this before on other systems. > That's the trouble with Boost; even after you find the right location, > the name of the library itself can still vary. Presumably this is why > the FindBoost.cmake module is ~500 lines long... And also why it gives the full path to each library, which is unusual. > Sorry, shouldn't have said brittle logic. It's really just this > naming business. I was suggesting to disable it because as it stands, > by default the build will fail on OS X using CMake 2.4. Is there a > way to get the full path to the library in 2.4? That would fix it. > Alternatively, we could just disable it when building on OS X. I've disabled boost by default under 2.4 on OS X. I've also added an option to tell it to use the multithreaded libs (i.e. append -mt to the lib names) under 2.4, which is on by default for OS X. This suffix is configurable in ccmake as an advanced option to allow for other weird ones. Brian Gerkey wrote: > And thanks again for getting us moved over to CMake. I'm very > impressed with the whole system, no matter whatever little hiccups > we're finding. I'd hate to be trying to fix this sort of thing with autotools... Geoff |