Re: [Oiio-dev] Windows 10 'x64' build in progress

[Larry Gritz]

Vcpkg ought to be able to install ocio for you as well.

I don't know which version of OIIO you are trying to build, but if it's 2.1 or 
later, you ought to be able to use OpenColorIO_ROOT rather than the other 
variables (assuming that there's a single point where the include files are 
underneath in /include and the ocio libraries are in /lib). That would be the 
more modern cmake way, rather than having to hint OPENCOLORIO_INCLUDE_DIR and 
OPENCOLORIO_LIBRARY separately.



> On Jun 19, 2020, at 3:48 AM, till dechent  wrote:
> 
> OpenColorIO is its own project and not included in OIIO. So you'll have to 
> acquire or compile that first: https://opencolorio.org/ 
> 
> 
> OPENCOLORIO_INCLUDE_DIR then needs to point to where your OCIO include files 
> are and the other one to the lib files.
> 
> If CMake can't find them it compiles without OCIO. 
> 
> Am Fr., 19. Juni 2020 um 11:22 Uhr schrieb Jovce Malakovski 
> mailto:jovc...@gmail.com>>:
> No, I just set USE_PYTHON = false
> What values should these two have?
> 
> On Fri, Jun 19, 2020 at 12:10 PM till dechent  > wrote:
> Did you set OPENCOLORIO_INCLUDE_DIR and OPENCOLORIO_LIBRARY in CMake?
> 
> Am Fr., 19. Juni 2020 um 09:38 Uhr schrieb Jovce Malakovski 
> mailto:jovc...@gmail.com>>:
> Thanks for the guide. I was able to make a visual studio project and then 
> build the oiiotool.
> One problem that I have is that the oiiotool builds without OpenColorIO. Im 
> getting this message No OpenColorIO support was enabled at build time
> 
> Do you have an idea how to include the OCIO support?
> 
> 
> On Sun, Apr 5, 2020 at 3:13 PM till dechent  > wrote:
> Hi,
> 
> I have done a quick write-up on how to build on Windows.
> 
> https://github.com/ttddee/ttddee.github.io/blob/master/building-oiio-win.md 
> 
> 
> Hope it helps someone.
> 
> Happy sunday!
> 
> Till 
> 
> Am So., 5. Apr. 2020 um 02:40 Uhr schrieb Larry Gritz  >:
> That's great news!
> 
> If you have any specific advice or step-by-step, or while it's fresh in your 
> head, please do look at our INSTALL instructions and if there are any 
> specific improvements, we would be very happy to incorporate your suggestions.
> 
> 
>> On Apr 2, 2020, at 1:42 PM, Simon Ashby > > wrote:
>> 
>> Just to report -- SUCCESS!!
>> After many days staring up at the cliff-face without seeing a path, not even 
>> a crack in the surface, suddenly I find that I am on top of the cliff 
>> looking around ," Wow! I can see really far from here, right into the 
>> future!"
>> 
>> I have been trying to build OpenIIO (and thus OpenColorio) on Windows-x64 
>> with Visual Studio 2019 (latest)  Basically it seems that VCKG got itself 
>> organized and the magic happened. I don't know if it was my efforts at 
>> resolving multiple dependencies that fed into over the web to the 
>> maintainers, but when I built afresh with a new Visual Studio, fresh CMAKE 
>> and VCPKG. it worked! 
>> 
>> Vcpkg handled the lot as far as Configuring went (and I assume Generation, 
>> it happens under the VS hood). It certainly couldn't do that last week. 
>> Anyway, I built a new project with Visual Studio using OOIO's example 
>> iconvert.cpp and it compiled exactly as expected, and it did the business.
>> Well done all contributors!!!  
>> 
>> So, take heart if you are struggling.. Talk to these guys here, and anyone 
>> who makes sense, back-up everything, rebuild your system clean, and it will 
>> work. Then you can put it all back in again, so your other stuff works...
>>
>> (Now ... on with our own app-specific stuff!)
>>   
>> Best health wishes to all
>> Simon A
>> 
>> Simon R Ashby
>> 3, Waters Meet
>> Huntingdon
>> Cambridgeshire 
>> PE29 3AY
>> +44(0)7775-815561 mobile
>> sra.luma...@gmail.com 
>> 
>> 
>> 
>> On Fri, 27 Mar 2020 at 21:40, Simon Ashby > > wrote:
>> >> do a write-up about how to compile it 
>> That would indeed be magic. My Colorio trouble:
>> - first: I can't find a Glut path that Configure will accept; it finds 
>> either Glut or Glew but not both; 
>> - and for each of expat, ilmbase and yamlcpp I get a git error!  
>> 
>> 1>-- Build started: Project: yamlcpp_install, Configuration: Debug x64 
>> --
>> 1>Performing download step (git clone) for 'yamlcpp_install'
>> 1>Cloning into 'yamlcpp_install'...
>> 1>HEAD is now at 9a36242 Update version to 0.6.3.
>> 1>fatal: 'submodule' appears to be a git command, but we were not
>> 1>able to execute it. Maybe git-submodule is broken?
>> 1>CMake Error at 
>> C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/tmp/yamlcpp_install-gitclone.cmake:52
>>  (message):
>> 1>  Failed to update submodules in:
>> 1>  'C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/src/yamlcpp_install'
>> 1>
>> 1>C:\Program 

Re: [Oiio-dev] Windows 10 'x64' build in progress

[Jovce Malakovski]

No, I just set USE_PYTHON = false
What values should these two have?

On Fri, Jun 19, 2020 at 12:10 PM till dechent 
wrote:

> Did you set OPENCOLORIO_INCLUDE_DIR and OPENCOLORIO_LIBRARY in CMake?
>
> Am Fr., 19. Juni 2020 um 09:38 Uhr schrieb Jovce Malakovski <
> jovc...@gmail.com>:
>
>> Thanks for the guide. I was able to make a visual studio project and then
>> build the oiiotool.
>> One problem that I have is that the oiiotool builds without OpenColorIO.
>> Im getting this message *No OpenColorIO support was enabled at build
>> time*
>>
>> Do you have an idea how to include the OCIO support?
>>
>>
>> On Sun, Apr 5, 2020 at 3:13 PM till dechent 
>> wrote:
>>
>>> Hi,
>>>
>>> I have done a quick write-up on how to build on Windows.
>>>
>>>
>>> https://github.com/ttddee/ttddee.github.io/blob/master/building-oiio-win.md
>>>
>>> Hope it helps someone.
>>>
>>> Happy sunday!
>>>
>>> Till
>>>
>>> Am So., 5. Apr. 2020 um 02:40 Uhr schrieb Larry Gritz >> >:
>>>
 That's great news!

 If you have any specific advice or step-by-step, or while it's fresh in
 your head, please do look at our INSTALL instructions and if there are any
 specific improvements, we would be very happy to incorporate your
 suggestions.


 On Apr 2, 2020, at 1:42 PM, Simon Ashby  wrote:

 Just to report -- SUCCESS!!
 After many days staring up at the cliff-face without seeing a path, not
 even a crack in the surface, suddenly I find that I am on top of the cliff
 looking around ," Wow! I can see really far from here, right into the
 future!"

 I have been trying to build OpenIIO (and thus OpenColorio)
 on Windows-x64 with Visual Studio 2019 (latest)  Basically it seems that
 VCKG got itself organized and the magic happened. I don't know if it was my
 efforts at resolving multiple dependencies that fed into over the web to
 the maintainers, but when I built afresh with a new Visual Studio, fresh
 CMAKE and VCPKG. it worked!

 Vcpkg handled the lot as far as Configuring went (and I assume
 Generation, it happens under the VS hood). It certainly couldn't do that
 last week. Anyway, I built a new project with Visual Studio using OOIO's
 example iconvert.cpp and it compiled exactly as expected, and it did the
 business.
 Well done all contributors!!!

 So, take heart if you are struggling.. Talk to these guys here, and
 anyone who makes sense, back-up everything, rebuild your system clean, and
 it will work. Then you can put it all back in again, so your other stuff
 works...

 (Now ... on with our own app-specific stuff!)

 Best health wishes to all
 Simon A

 Simon R Ashby
 3, Waters Meet
 Huntingdon
 Cambridgeshire
 PE29 3AY
 +44(0)7775-815561 mobile
 sra.luma...@gmail.com



 On Fri, 27 Mar 2020 at 21:40, Simon Ashby 
 wrote:

> >> do a write-up about how to compile it
> That would indeed be magic. My Colorio trouble:
> - first: I can't find a Glut path that Configure will accept; it finds
> either Glut or Glew but not both;
> - and for each of expat, ilmbase and yamlcpp I get a git error!
>
> 1>-- Build started: Project: yamlcpp_install, Configuration: Debug
> x64 --
> 1>Performing download step (git clone) for 'yamlcpp_install'
> 1>Cloning into 'yamlcpp_install'...
> 1>HEAD is now at 9a36242 Update version to 0.6.3.
> 1>fatal: 'submodule' appears to be a git command, but we were not
> 1>able to execute it. Maybe git-submodule is broken?
> 1>CMake Error at
> C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/tmp/yamlcpp_install-gitclone.cmake:52
> (message):
> 1>  Failed to update submodules in:
> 1>
>  'C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/src/yamlcpp_install'
> 1>
> 1>C:\Program Files (x86)\Microsoft Visual
> Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5):
> error MSB6006: "cmd.exe" exited with code 1.
> 1>Done building project "yamlcpp_install.vcxproj" -- FAILED.
> == Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped
> ==
>
> As I said I'm going to have another go at a fresh download and build
> if OiiO itself.
>
> Best health wishes to all
> Simon A
>
> Simon R Ashby
> 3, Waters Meet
> Huntingdon
> Cambridgeshire
> PE29 3AY
> +44(0)7775-815561 mobile
> sra.luma...@gmail.com
>
>
>
> On Fri, 27 Mar 2020 at 16:37, till dechent 
> wrote:
>
>> As I said I haven't touched OCIO in a while so I am not sure how it
>> works with the current version.
>>
>> But OIIO should definitely work. I have been wanting to do a write-up
>> about how to compile it because the documentation is so outdated on the
>> Windows side.
>>
>> Maybe I'll actually do that :p
>>

Re: [Oiio-dev] Windows 10 'x64' build in progress

[till dechent]

Did you set OPENCOLORIO_INCLUDE_DIR and OPENCOLORIO_LIBRARY in CMake?

Am Fr., 19. Juni 2020 um 09:38 Uhr schrieb Jovce Malakovski <
jovc...@gmail.com>:

> Thanks for the guide. I was able to make a visual studio project and then
> build the oiiotool.
> One problem that I have is that the oiiotool builds without OpenColorIO.
> Im getting this message *No OpenColorIO support was enabled at build time*
>
> Do you have an idea how to include the OCIO support?
>
>
> On Sun, Apr 5, 2020 at 3:13 PM till dechent 
> wrote:
>
>> Hi,
>>
>> I have done a quick write-up on how to build on Windows.
>>
>>
>> https://github.com/ttddee/ttddee.github.io/blob/master/building-oiio-win.md
>>
>> Hope it helps someone.
>>
>> Happy sunday!
>>
>> Till
>>
>> Am So., 5. Apr. 2020 um 02:40 Uhr schrieb Larry Gritz > >:
>>
>>> That's great news!
>>>
>>> If you have any specific advice or step-by-step, or while it's fresh in
>>> your head, please do look at our INSTALL instructions and if there are any
>>> specific improvements, we would be very happy to incorporate your
>>> suggestions.
>>>
>>>
>>> On Apr 2, 2020, at 1:42 PM, Simon Ashby  wrote:
>>>
>>> Just to report -- SUCCESS!!
>>> After many days staring up at the cliff-face without seeing a path, not
>>> even a crack in the surface, suddenly I find that I am on top of the cliff
>>> looking around ," Wow! I can see really far from here, right into the
>>> future!"
>>>
>>> I have been trying to build OpenIIO (and thus OpenColorio)
>>> on Windows-x64 with Visual Studio 2019 (latest)  Basically it seems that
>>> VCKG got itself organized and the magic happened. I don't know if it was my
>>> efforts at resolving multiple dependencies that fed into over the web to
>>> the maintainers, but when I built afresh with a new Visual Studio, fresh
>>> CMAKE and VCPKG. it worked!
>>>
>>> Vcpkg handled the lot as far as Configuring went (and I assume
>>> Generation, it happens under the VS hood). It certainly couldn't do that
>>> last week. Anyway, I built a new project with Visual Studio using OOIO's
>>> example iconvert.cpp and it compiled exactly as expected, and it did the
>>> business.
>>> Well done all contributors!!!
>>>
>>> So, take heart if you are struggling.. Talk to these guys here, and
>>> anyone who makes sense, back-up everything, rebuild your system clean, and
>>> it will work. Then you can put it all back in again, so your other stuff
>>> works...
>>>
>>> (Now ... on with our own app-specific stuff!)
>>>
>>> Best health wishes to all
>>> Simon A
>>>
>>> Simon R Ashby
>>> 3, Waters Meet
>>> Huntingdon
>>> Cambridgeshire
>>> PE29 3AY
>>> +44(0)7775-815561 mobile
>>> sra.luma...@gmail.com
>>>
>>>
>>>
>>> On Fri, 27 Mar 2020 at 21:40, Simon Ashby  wrote:
>>>
 >> do a write-up about how to compile it
 That would indeed be magic. My Colorio trouble:
 - first: I can't find a Glut path that Configure will accept; it finds
 either Glut or Glew but not both;
 - and for each of expat, ilmbase and yamlcpp I get a git error!

 1>-- Build started: Project: yamlcpp_install, Configuration: Debug
 x64 --
 1>Performing download step (git clone) for 'yamlcpp_install'
 1>Cloning into 'yamlcpp_install'...
 1>HEAD is now at 9a36242 Update version to 0.6.3.
 1>fatal: 'submodule' appears to be a git command, but we were not
 1>able to execute it. Maybe git-submodule is broken?
 1>CMake Error at
 C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/tmp/yamlcpp_install-gitclone.cmake:52
 (message):
 1>  Failed to update submodules in:
 1>
  'C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/src/yamlcpp_install'
 1>
 1>C:\Program Files (x86)\Microsoft Visual
 Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5):
 error MSB6006: "cmd.exe" exited with code 1.
 1>Done building project "yamlcpp_install.vcxproj" -- FAILED.
 == Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped
 ==

 As I said I'm going to have another go at a fresh download and build if
 OiiO itself.

 Best health wishes to all
 Simon A

 Simon R Ashby
 3, Waters Meet
 Huntingdon
 Cambridgeshire
 PE29 3AY
 +44(0)7775-815561 mobile
 sra.luma...@gmail.com



 On Fri, 27 Mar 2020 at 16:37, till dechent 
 wrote:

> As I said I haven't touched OCIO in a while so I am not sure how it
> works with the current version.
>
> But OIIO should definitely work. I have been wanting to do a write-up
> about how to compile it because the documentation is so outdated on the
> Windows side.
>
> Maybe I'll actually do that :p
>
> Am Fr., 27. März 2020 um 16:08 Uhr schrieb Simon Ashby <
> sra.luma...@gmail.com>:
>
>> I don't see anywhere to control project options in Cmake?
>> This will make you laugh - I didn't realise that CMakeGUI doesn't
>> actually execute the build, it 

Re: [Oiio-dev] Windows 10 'x64' build in progress

[Jovce Malakovski]

Thanks for the guide. I was able to make a visual studio project and then
build the oiiotool.
One problem that I have is that the oiiotool builds without OpenColorIO. Im
getting this message *No OpenColorIO support was enabled at build time*

Do you have an idea how to include the OCIO support?


On Sun, Apr 5, 2020 at 3:13 PM till dechent  wrote:

> Hi,
>
> I have done a quick write-up on how to build on Windows.
>
> https://github.com/ttddee/ttddee.github.io/blob/master/building-oiio-win.md
>
> Hope it helps someone.
>
> Happy sunday!
>
> Till
>
> Am So., 5. Apr. 2020 um 02:40 Uhr schrieb Larry Gritz :
>
>> That's great news!
>>
>> If you have any specific advice or step-by-step, or while it's fresh in
>> your head, please do look at our INSTALL instructions and if there are any
>> specific improvements, we would be very happy to incorporate your
>> suggestions.
>>
>>
>> On Apr 2, 2020, at 1:42 PM, Simon Ashby  wrote:
>>
>> Just to report -- SUCCESS!!
>> After many days staring up at the cliff-face without seeing a path, not
>> even a crack in the surface, suddenly I find that I am on top of the cliff
>> looking around ," Wow! I can see really far from here, right into the
>> future!"
>>
>> I have been trying to build OpenIIO (and thus OpenColorio) on Windows-x64
>> with Visual Studio 2019 (latest)  Basically it seems that VCKG got itself
>> organized and the magic happened. I don't know if it was my efforts at
>> resolving multiple dependencies that fed into over the web to the
>> maintainers, but when I built afresh with a new Visual Studio, fresh CMAKE
>> and VCPKG. it worked!
>>
>> Vcpkg handled the lot as far as Configuring went (and I assume
>> Generation, it happens under the VS hood). It certainly couldn't do that
>> last week. Anyway, I built a new project with Visual Studio using OOIO's
>> example iconvert.cpp and it compiled exactly as expected, and it did the
>> business.
>> Well done all contributors!!!
>>
>> So, take heart if you are struggling.. Talk to these guys here, and
>> anyone who makes sense, back-up everything, rebuild your system clean, and
>> it will work. Then you can put it all back in again, so your other stuff
>> works...
>>
>> (Now ... on with our own app-specific stuff!)
>>
>> Best health wishes to all
>> Simon A
>>
>> Simon R Ashby
>> 3, Waters Meet
>> Huntingdon
>> Cambridgeshire
>> PE29 3AY
>> +44(0)7775-815561 mobile
>> sra.luma...@gmail.com
>>
>>
>>
>> On Fri, 27 Mar 2020 at 21:40, Simon Ashby  wrote:
>>
>>> >> do a write-up about how to compile it
>>> That would indeed be magic. My Colorio trouble:
>>> - first: I can't find a Glut path that Configure will accept; it finds
>>> either Glut or Glew but not both;
>>> - and for each of expat, ilmbase and yamlcpp I get a git error!
>>>
>>> 1>-- Build started: Project: yamlcpp_install, Configuration: Debug
>>> x64 --
>>> 1>Performing download step (git clone) for 'yamlcpp_install'
>>> 1>Cloning into 'yamlcpp_install'...
>>> 1>HEAD is now at 9a36242 Update version to 0.6.3.
>>> 1>fatal: 'submodule' appears to be a git command, but we were not
>>> 1>able to execute it. Maybe git-submodule is broken?
>>> 1>CMake Error at
>>> C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/tmp/yamlcpp_install-gitclone.cmake:52
>>> (message):
>>> 1>  Failed to update submodules in:
>>> 1>  'C:/git/OpenColorIO/out/build/ext/build/yaml-cpp/src/yamlcpp_install'
>>> 1>
>>> 1>C:\Program Files (x86)\Microsoft Visual
>>> Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(231,5):
>>> error MSB6006: "cmd.exe" exited with code 1.
>>> 1>Done building project "yamlcpp_install.vcxproj" -- FAILED.
>>> == Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped
>>> ==
>>>
>>> As I said I'm going to have another go at a fresh download and build if
>>> OiiO itself.
>>>
>>> Best health wishes to all
>>> Simon A
>>>
>>> Simon R Ashby
>>> 3, Waters Meet
>>> Huntingdon
>>> Cambridgeshire
>>> PE29 3AY
>>> +44(0)7775-815561 mobile
>>> sra.luma...@gmail.com
>>>
>>>
>>>
>>> On Fri, 27 Mar 2020 at 16:37, till dechent 
>>> wrote:
>>>
 As I said I haven't touched OCIO in a while so I am not sure how it
 works with the current version.

 But OIIO should definitely work. I have been wanting to do a write-up
 about how to compile it because the documentation is so outdated on the
 Windows side.

 Maybe I'll actually do that :p

 Am Fr., 27. März 2020 um 16:08 Uhr schrieb Simon Ashby <
 sra.luma...@gmail.com>:

> I don't see anywhere to control project options in Cmake?
> This will make you laugh - I didn't realise that CMakeGUI doesn't
> actually execute the build, it just makes the makefiles
> and as you said, the prj and sln files! So I had thought that after
> Configure, I could just press Generate and it would generate the target
> libs! Spent some time wondering why it didn't create any files... (newbie
> indeed, but how is anyone to know?)
>

Re: [Oiio-dev] Setting ImageCache memory size limits via Python bindings

[Larry Gritz]

Note for those following along: we're having an off-list discussion about this. 
We'll summarize any useful general advice when we have it figured out, but 
right now there are a number of red herrings to figure out.

-- lg


> On Jun 17, 2020, at 5:47 PM, Frank Du  wrote:
> 
> Hi all,
> 
> I came across this useful thread
> 
> http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2016-August/000593.html
>  
> 
> 
> We have a process in Python that can end up handling quite a few separate 
> image files (30+) and they're all opened via ImageBuf. I noticed that the 
> process is hitting the 4GB limit set in the thread above. How can I decrease 
> the global ImageCache memory size in Python?
> 
> - Frank

--
Larry Gritz
l...@larrygritz.com




___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org