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 <till.dech...@gmail.com> > 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 <l...@larrygritz.com >> >: >> >>> 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 <sra.luma...@gmail.com> 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 <sra.luma...@gmail.com> 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 <till.dech...@gmail.com> >>>> 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?) >>>>>> >>>>>> ( btw What path do I put into GLEW_DIR? Which directory is CMAKEGUI >>>>>> expecting here? It says GLEW not found for every \include and \bin,I >>>>>> tried, >>>>>> and a few others. Cmakegui says use 'The directory with the makefile in >>>>>> it' >>>>>> --- well, there are 468 ColorIO\ folders with *MAKE*.* titles. (VCPKG >>>>>> says >>>>>> GLEW is already installed.) >>>>>> >>>>>> The funniest part is, that even when I loaded VStudio and tried to >>>>>> build the project, it failed at the first command: >>>>>> fatal: 'submodule' appears to be a git command, but we were not >>>>>> able to execute it. Maybe git-submodule is broken? >>>>>> >>>>>> I am pausing now, now going back to build OpenImageIO and see if that >>>>>> fixes anything. >>>>>> >>>>>> Best health wishes to all >>>>>> Simon A >>>>>> >>>>>> On Fri, 27 Mar 2020 at 15:11, till dechent <till.dech...@gmail.com> >>>>>> wrote: >>>>>> > >>>>>> > I don't know, never compiled it with Nuke. That dependency should >>>>>> be optional? >>>>>> > >>>>>> > Am Fr., 27. März 2020 um 13:38 Uhr schrieb Simon Ashby < >>>>>> sra.luma...@gmail.com>: >>>>>> >> >>>>>> >> Do you know, colorio asks for Nuke,do you know if this is the nuke >>>>>> SDK on >>>>>> >> https://www.foundry.com/products/nuke/developers? >>>>>> >> >>>>>> >> ...not my industry, d'y'see... >>>>>> >> >>>>>> >> Best health wishes to all >>>>>> >> Simon A >>>>>> >> >>>>>> >>>>>> >> >>>>>> >>>>>> >>>>>> 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 15:11, till dechent <till.dech...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> I don't know, never compiled it with Nuke. That dependency should be >>>>>>> optional? >>>>>>> >>>>>>> Am Fr., 27. März 2020 um 13:38 Uhr schrieb Simon Ashby < >>>>>>> sra.luma...@gmail.com>: >>>>>>> >>>>>>>> Do you know, colorio asks for Nuke,do you know if this is the nuke >>>>>>>> SDK on >>>>>>>> https://www.foundry.com/products/nuke/developers? >>>>>>>> >>>>>>>> ...not my industry, d'y'see... >>>>>>>> >>>>>>>> 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 12:08, till dechent <till.dech...@gmail.com> >>>>>>>> wrote: >>>>>>>> > >>>>>>>> > Hey Simon, >>>>>>>> > >>>>>>>> > yes the most used build environment for OIIO is Linux but, as I >>>>>>>> said, the Windows builds have been pretty smooth lately. >>>>>>>> > >>>>>>>> > Apparently you will have to remove old CMake versions to use the >>>>>>>> new installer. Or maybe see if an older release works and gets the GUI >>>>>>>> working for you: https://github.com/Kitware/CMake/releases >>>>>>>> > >>>>>>>> > Sounds like you have a lot of stuff installed. Maybe you can >>>>>>>> start on a fresh system or compile in a VM? >>>>>>>> > >>>>>>>> > I haven't built OpenColorIO in a while but it should be pretty >>>>>>>> similar. >>>>>>>> > >>>>>>>> > 1. I always just install the missing packages manually. One >>>>>>>> important thing about Vcpkg is that it does not default to the 64bit >>>>>>>> version. So unless you tell it otherwise it will install 32bit >>>>>>>> libraries. >>>>>>>> > >>>>>>>> > To get the x64 version of libraw f.e. you do this: vcpkg install >>>>>>>> libraw:x64-windows >>>>>>>> > >>>>>>>> > Then when you add the path to the lib in CMake you point it to >>>>>>>> C:\...\vcpkg\installed\x64-windows\lib >>>>>>>> > >>>>>>>> > 2. If you hit configure in CMake it will complain about all the >>>>>>>> deps it cannot find in your path. Then you can set those manually. >>>>>>>> Some are >>>>>>>> optional, depending on what you need. >>>>>>>> > >>>>>>>> > Check out the screenshot, that's how it is going to look like. >>>>>>>> > >>>>>>>> > Cheers >>>>>>>> > >>>>>>>> > Till >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > Am Fr., 27. März 2020 um 11:28 Uhr schrieb Simon Ashby < >>>>>>>> sra.luma...@gmail.com>: >>>>>>>> >> >>>>>>>> >> Thanks for this quick response - Till (hope that's the right >>>>>>>> name :-). >>>>>>>> >> >>>>>>>> >> cmake GUI? >>>>>>>> >> Wow! Must get... >>>>>>>> >> Ah - cmake website says 'uninstall ver 3.4 first'. >>>>>>>> >> Hmmm.. Cmake is not known to Windows as an app.. wonder >>>>>>>> where it is? >>>>>>>> >> - And - ?have MSVStudio and vpkg installed a few >>>>>>>> versions of >>>>>>>> >> their own, like they >>>>>>>> >> did with git (I found 12 versions of that yesterday). >>>>>>>> >> >>>>>>>> >> Lets see how I get on. encouraging to hear your confidence, I >>>>>>>> have >>>>>>>> >> been working through this >>>>>>>> >> install for 3 days now. I assumed the problems were because it >>>>>>>> was a >>>>>>>> >> Linux native build -- unfair? >>>>>>>> >> >>>>>>>> >> BTW have you worked through Colorio as well? That is giving >>>>>>>> similar >>>>>>>> >> dependency issues. >>>>>>>> >> >>>>>>>> >> Two (newbie) questions: (just send links if you are busy) >>>>>>>> >> 1. With a build's missing dependency, can you open a console at >>>>>>>> the >>>>>>>> >> tree root and >>>>>>>> >> run vcpkg (...some commandline args...) to resolve those >>>>>>>> dependency >>>>>>>> >> issues semi-automatically? >>>>>>>> >> Does vcpg interpret the original project 's makefiles to do this? >>>>>>>> >> >>>>>>>> >> 2. Environment variables - there seem to be many needed:( I last >>>>>>>> used >>>>>>>> >> these with MS-DOS) >>>>>>>> >> - What are the crucial variables/paths to set? >>>>>>>> >> - Do you put these in system or user space, >>>>>>>> >> - Do you wrap these settings in a batch/cmd file around the >>>>>>>> >> makefile/vcpkg call or permanently? >>>>>>>> >> >>>>>>>> >> I admit that after manually using 'vcpkg install xxx' to resolve >>>>>>>> >> several dozen or so nested missing >>>>>>>> >> dependencies across co-reliant LibRaw, OIIO and OpenColorIO >>>>>>>> projects I >>>>>>>> >> keep pausing to wonder, 'What >>>>>>>> >> am I doing wrong?' and ' How do others do this?' and 'Am I the >>>>>>>> first >>>>>>>> >> to be doing this combination of builds?' >>>>>>>> >> (Not complaining - I just wanna get on with our app code!) >>>>>>>> >> >>>>>>>> >> 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 10:48, till dechent < >>>>>>>> till.dech...@gmail.com> wrote: >>>>>>>> >> > >>>>>>>> >> > Hi Simon, >>>>>>>> >> > >>>>>>>> >> > for the last couple of versions building on Windows has been >>>>>>>> really straight forward and worked without issues for me. >>>>>>>> >> > >>>>>>>> >> > Basic rundown: >>>>>>>> >> > >>>>>>>> >> > - Install dependencies (I use Vcpkg for that) >>>>>>>> >> > >>>>>>>> >> > - Get cmake (https://cmake.org/download/), open the project, >>>>>>>> set your options and hit configure. All this can be done in CMake GUI. >>>>>>>> >> > >>>>>>>> >> > - CMake creates a Visual Studio Project. Open in VS, set to >>>>>>>> Release and build. You might want to set your CMAKE_INSTALL_DIR, I >>>>>>>> think it >>>>>>>> defaults to c:\something... >>>>>>>> >> > >>>>>>>> >> > If you get stuck or need more details, don't hesitate to get >>>>>>>> in touch. >>>>>>>> >> > >>>>>>>> >> > Cheers >>>>>>>> >> > >>>>>>>> >> > Till >>>>>>>> >> > >>>>>>>> >> > Am Fr., 27. März 2020 um 09:47 Uhr schrieb Simon Ashby < >>>>>>>> sra.luma...@gmail.com>: >>>>>>>> >> >> >>>>>>>> >> >> Just joined this list ('Hi Larry') >>>>>>>> >> >> Windows 10 'x64' build in progress: Happy to hear from anyone >>>>>>>> doing this... >>>>>>>> >> >> >>>>>>>> >> >> Before asking specific questions on roadblocks I would >>>>>>>> appreciate advice: >>>>>>>> >> >> - Should I even be trying a Win 64 OIIO build? Is there a >>>>>>>> show-stopper? >>>>>>>> >> >> - The best way to feed back what I encounter so far. >>>>>>>> >> >> - Which logs help you guys most - and do you really want the >>>>>>>> entire build logs? >>>>>>>> >> >> - One thing - a tool to map out what the make structure is in >>>>>>>> a >>>>>>>> >> >> particular tree. This >>>>>>>> >> >> tree seems littered with large and small make-related files >>>>>>>> with >>>>>>>> >> >> various extensions. >>>>>>>> >> >> - Is there a decent tutorial guide to cmake, to help me get an >>>>>>>> >> >> overview of what the >>>>>>>> >> >> package builders intended? >>>>>>>> >> >> - Alternatively, if the make structure in the package has >>>>>>>> become >>>>>>>> >> >> degraded over time, does >>>>>>>> >> >> anyone know a guide(link) to best practice. This will help me >>>>>>>> see >>>>>>>> >> >> what's good and what's >>>>>>>> >> >> perhaps 'sub-optimal' - that'll help me suggest sensible >>>>>>>> fixes. >>>>>>>> >> >> >>>>>>>> >> >> Jargon Level: I haven't used make since the 90s and am new to >>>>>>>> Cmake projects; >>>>>>>> >> >> Have been using Visual Studio, with git, GitDesktop and VCPKG >>>>>>>> to get libs etc. >>>>>>>> >> >> OK with C/C++ and have used python (mostly 3.x recently, but >>>>>>>> now I am >>>>>>>> >> >> working in VFX :-) >>>>>>>> >> >> I have installed dual-boot Arch-Linux in case that is useful >>>>>>>> (it's >>>>>>>> >> >> Manjaro, so far unused) . >>>>>>>> >> >> (also have a MacBook FWIW) >>>>>>>> >> >> >>>>>>>> >> >> Best health wishes to all >>>>>>>> >> >> Simon A >>>>>>>> >> >> Lumavec (UK) >>>>>>>> >> >> _______________________________________________ >>>>>>>> >> >> 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 >>> >>> >>> -- >>> Larry Gritz >>> l...@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 >
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
