Hi!
First, which procedure is it that you're following exactly (where is it
written down, somewhere on the wiki?)
I have been following
http://openimageio.org/wiki/index.php?title=Building_OpenImageIO_on_Windows
If the USE_TBB option is activated, oiio will build with the bundled TBB
for atomic support and a few other things. If not, it'll try to use
some simple atomic support built into OIIO. You shouldn't have to set
any path here, and either option should work I think.
Yes, either option works, except on windows VS needs to somehow know
where the lib is. I guess on linux tbb is found automatically via
cmake?! Should it be automatically found on windows too and added lo
LIBPATH?
Yeah we need to fix OIIO for more recent boost versions I suppose. I
recently fixed the same problem in another project, in that case I made
it compatible with both versions but it was a bit of a pain. Please
open an issue on the tracker.
There is actually just one issue while adding a recent path to the menu
in iv, everything else compiles fine with a new boost.
I imagine this would be welcome, though someone else will have to chime
in.
Yes, I guess so because you have to compile all the dependencies
yourself (at least here on my ubuntu machine I can get all of them via
the package manager), which is quite painful for somebody not
experienced with this.
Cheers
Sebastian
--
Sebastian Elsner - Pipeline TD - r i s e | fx
t: +49 30 201 803 00 [email protected]
c: +49 175 336 5739 7548 www.risefx.com
r i s e | fx GmbH
Schlesische Strasse 28, Aufgang B 10997 Berlin
Richard-Byrd-Strasse 12, 50829 Cologne
Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow
Handelsregister Berlin HRB 106667 B
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
