I think currently, using boost is the most convenient way to get this
working on windows.
Maybe when VS2010 gets more usage out there that would change... but
then, so can the default in OCIO :-)


On Apr 16, 10:25 am, Jeremy Selan <jeremy...@...> wrote:

Has anyone on this list built OCIO for Windows, and NOT used boost_ptr?

If so, we'd love to hear from you.

(If we don't hear back, that will be an implied LGTM)... ;)

-- Jeremy







On Mon, Apr 16, 2012 at 9:30 AM, Larry Gritz <l....@...> wrote:

Doesn't the boost package use tr1 underneath when it detects a compiler that's known to support it?
So that would be equivalent, IIRC.

On Apr 14, 2012, at 3:05 AM, Malcolm Humphreys wrote:

I think it would be best to package boost smart pointer headers with ocio and use it all the time over tr1 on all platforms.

LaszloSebo <laszl...@...> wrote:

Hi there,

When building OpenColorIO on windows, one of the things i had to
change to make things properly build in my environment was enabling
boost in the config, by setting the OCIO_USE_BOOST_PTR CMakeLists
option to ON.

Currently in the base setup this setting defaults to off to minimize
custom dependencies, so by default OCIO uses tr1 for the pointers.
Using vanilla visual studio 2008 as a compiler, tr1 is not available.

Polling other windows devs, do you think boost should default to ON?
There are ways to get tr1 working on windows without boost (for
example, using the visual studio feature pack for 2008, or using
visual studio 2010), so its not a straightforward answer.

Also, its not a big deal to manually define this setting should you
want to use boost, or even add your libs/includes manually.

What do you think? Should OCIO default to boost=ON on windows? Should
it have a more complex identification of compiler/installed libs
available upon config, and set this setting accordingly?

cheers,
laszlo

--
Larry Gritz
l....@...