This has only affected one of my 3 machines that I've built on so far,
since rebasing my git repo. This was a v1.40 boost install from
macports. Trying to find the boost threads library twice causes the
"Boost_THREAD_LIBRARY" variable to go from something like "/opt/local/
lib/libboost-thread-mt.dylib" from after the first call, to something
like "optimized;/opt/local/lib/libboost-thread-mt.dylib;debug;/opt/
local/lib/libboost-thread-mt.dylib". This of course, is Bad.
Stephen
| Attachment | Size |
|---|---|
| 0001-cmake-Prevent-double-find-of-boost-thread-package-on.patch | 987 bytes |
Patch for build bug on Mac OS XSnow Leopard
On Mon, Nov 2, 2009 at 17:01, S Roderick <kiwi [dot] net [..] ...> wrote:
> This has only affected one of my 3 machines that I've built on so far,
> since rebasing my git repo. This was a v1.40 boost install from macports.
> Trying to find the boost threads library twice causes the
> "Boost_THREAD_LIBRARY" variable to go from something like
> "/opt/local/lib/libboost-thread-mt.dylib" from after the first call, to
> something like
> "optimized;/opt/local/lib/libboost-thread-mt.dylib;debug;/opt/local/lib/libboost-thread-mt.dylib".
> This of course, is Bad.
>
Thinking about this again, I believe this is valid 'cmake style' for this
variable (it may be a list of optimized/debug versions). Maybe our pkgconfig
generation needs to be fixed...again.
Peter