Re: Compilation fail on FC13

Jeremy Selan <jeremy...@...>

Actually, I dont believe there currently is a link dependency to boost.

ldd src/core/ : => (0x00007fff63afb000) => /usr/lib64/ (0x00007f4b3241a000) => /lib64/ (0x00007f4b32196000) => /usr/lib64/ (0x00007f4b31f80000) => /lib64/ (0x00007f4b31c30000)
/lib64/ (0x00007f4b329e5000)

And, a bit surprisingly, even the unit test program doesnt appear to
link to boost:
ldd src/core/ocio_core_tests: => (0x00007fff09fb8000) => (0x00007f41d812d000) => /usr/lib64/ (0x00007f41d7e1f000) => /lib64/ (0x00007f41d7b9c000) => /usr/lib64/ (0x00007f41d7986000) => /lib64/ (0x00007f41d7636000)
/lib64/ (0x00007f41d83b3000)

So the only benefit would be to remove it as a compile time dependency
(presuming that we dont let anyone use at link time, either).

-- Jeremy

On Mon, Sep 20, 2010 at 2:35 PM, Alan Jones <sky...@...> wrote:
Hi Jeremy,

On Mon, Sep 20, 2010 at 4:10 PM, Jeremy Selan <jeremy...@...> wrote:
I've also been rethinking the use of boost within OCIO.  Currently
there are only two things we use it for: shared_ptr and the unit test
shared_ptr is header only and you're already using CMake, so perhaps
it'd be worth
looking at using CMake's unit testing instead of boost's?

This way there's no linking dependencies against boost.



Join to automatically receive all group messages.