I prefer solution one and appreciate it if you create a new stable tag for the
master branch.Cheers.
On Thursday, October 10, 2019, 11:03:50 AM PDT, Larry Gritz
<l...@larrygritz.com> wrote:
Yes, I recently ran across this and fixed in in master:
https://github.com/OpenImageIO/oiio/pull/2350
Unfortunately, I don't think the fix can be safely back-ported to 2.0 releases
without introducing an ABI incompatibility, because the fix required changing
some declarations and data members of a public class.
The solutions I can recommend are either (1) build and use OIIO master branch
(I can make a stable tag for a developer preview release if you want, so there
is a fixed place to sync to rather than the daily master); or (2) use the OIIO
2.0 releases, but compile with the older MSVS. I *think* that MSVS gives you
the option of selecting which MSVS compatibility version you want, so even
though you have MSVS 16.3.3 installed, you can compile OIIO with an older
version, they are all included together if I understand correctly.
-- lg
On Oct 10, 2019, at 10:49 AM, Morteza Ramezanali <xdreamerm...@yahoo.com> wrote:
Just upgraded to VS 16.3.3 and I am not able to build oiio from source anymore.
I think it has something to do with ImageBufImpl forward declaration and
ImageBuf.
Win10, VS 16.3.3 and CL 19.23.28106.4
The log is in the
attachment.Thanks.<install-x64-windows-dbg-out.log>_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--Larry grit...@larrygritz.com
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
