I totally don't understand this explanation (probably because I don't use
Windows), but if you email me (privately) the email address you use for your
google credentials, I'll give you permission to edit the wiki, and you should
add this file (and any others you think are important) as attachments as well
as edit the Windows compilation instructions in any way you think would be more
helpful.
-- lg
On Sep 21, 2011, at 12:21 AM, Sebastian Elsner wrote:
> The package in the email would be the libraries, includes and shared objects
> only for windows 64 bit compiled with (and only working) with Visual Studio
> 2008 SP1 in Release (means normally no debug information available)
> configuration. Windows 32bit is not included. What I do not like currently
> is, if we package the old externals.zip and my package win32 and win64 would
> use different library versions EXR 1.6.1 (32bit) vs. 1.7.0 (64bit) for
> example. I would like to fix this as well as include the Qt dlls so the
> deployment I created works out of the box (iv is crashing if the dlls are not
> in the PATH or in the same folder).
>
> So, this is something which will not happen immediately, first we have to
> test my externals and the compiled oiio in our own project (which has been in
> win32 so far too). Then I would like to update the 32bit externals to the
> newest library versions. This however depends on if this is OK with the
> project leads. Then update the wiki and merge 32 and 64 bit externals and
> upload them. Doing this bit by bit, the easiest thing would be to get an
> account for the wiki so I can update as necessary and not bug you constantly.
>
> cheers
>
> Sebastian
>
>
> On 09/21/2011 08:26 AM, Larry Gritz wrote:
>> I see that this file isn't so big after all. I can put it up where people
>> can download it.
>>
>> Should it *replace* the external.zip file that's already referenced, or
>> should it be in addition?
>>
>> Can you describe in simple terms for a child what the difference is between
>> the existing external.zip and the new one you reference in this email?
>>
>> -- lg
>>
>>
>> On Sep 20, 2011, at 9:23 AM, Sebastian Elsner wrote:
>>
>>> Hi everyone,
>>>
>>> it was quite a coincidence that Simon wrote to the list again and I also
>>> really needed to get the oiio win64 binaries finally working today, so I
>>> just zipped everything and uploaded it
>>> (https://rapidshare.com/files/2199959295/OpenImageIOvs2008x64release.7z).
>>> Along comes an extended HowTo, which we could include in the wiki. These
>>> descriptions are written along the existing wiki page, but different and
>>> extended on some levels. At some point I would really like to get both of
>>> them merged.
>>>
>>> @ Larry: How would I get an wiki account? Also to upload the externals to
>>> something more "stable".
>>> @ Simon: Hope this helps to get you started.
>>>
>>>
>>>
>>> Here are the build notes:
>>>
>>>
>>> Building OpenImageIO on Windows x64
>>>
>>> Here's instruction on how to build OpenImageIO on Windows.
>>>
>>> What You need
>>>
>>> Visual Studio 2008 (2005 may work but there is more work involved with
>>> the externals, especially openexr)
>>> Cmake (latest)
>>>
>>> Limitations:
>>> Currently jpg2000 support is broken for win64, because the x64 compiled
>>> jpg2000 library (libjasper) won't link with oiio
>>> These instructions do not cover Field3D support
>>>
>>>
>>> Instructions
>>>
>>> 1. Check out the trunk or a branch of your choice. The remainder of these
>>> instructions assume that you downloaded the latest stable (0.10.2) the
>>> R:\libraries\OpenImageIO\oiio-0.10.2 directory.
>>>
>>> 2. Download the precompiled external libraries. Please note: The libraries
>>> provided have different versions than the ones provided for win32. Next,
>>> unpack it. The directory with the downloaded code from the repository and
>>> the directory with unpacked libraries should be siblings. For example,
>>>
>>> D:
>>> \libraries
>>> \OpenImageIO
>>> \trunk // this is my tree
>>> \build // directory that is created by cmake
>>> \src // directory with src files for OIIO
>>>
>>> \external // this is extracted external package
>>> \dist
>>> \win64
>>> \glew-1.6.0
>>> \ilmbase-1.0.2
>>> \jasper-1.900.1
>>> \jpeg-8c
>>> \libpng-1.5.4
>>> \openexr-1.7.0
>>> \Python-2.6.7
>>> \tbb30_20110427oss
>>> \zlib-1.2.5
>>> \tiff-3.9.5
>>>
>>>
>>> 3. Download precompiled libraries (boost_1_45_0-vc64-bin.exe) from
>>> http://boost.teeks99.com/. We do not choose the newest version, because it
>>> will not work with current oiio, due to a changed API of the filesystem
>>> module. You can extract it anywhere you want. Be sure to set the BOOST_ROOT
>>> environment variable (R:\libraries\boost_1_45_0).
>>>
>>> 4. Setup Qt. This is optional and only needed if you want to use the GUI
>>> tools which come with oiio. Download the precompiled Qt4 binaries for
>>> Windows qt-win64-opensource-4.7.2-noqt3-vs2008.exe from
>>> http://code.google.com/p/qt-msvc-installer/downloads/list. Install to the
>>> standard location, other locations did not work here. Add the path to the
>>> Qt bin directory (C:\Qt\4.7.2_x64\bin) to the PATH variable. It's important
>>> to add the Qt bin directory to PATH because the FindQt4 module uses it to
>>> search for qmake applications. If not set, set QTDIR environment variable
>>> to the Qt home dir (C:\Qt\4.7.2_x64).
>>>
>>> 6. Install cmake. You can download precompiled cmake binaries. After
>>> installing, run cmake-gui. Set the field that specifies the source code
>>> location (for example, to R:\libraries\OpenImageIO\oiio-0.10.2\src). Then
>>> set the field that specifies "where to build the binaries" to the directory
>>> you want to build project for OIIO
>>> (R:\libraries\OpenImageIO\oiio-0.10.2\build).
>>>
>>> 7. Under options check supress dev warnings
>>>
>>> 8. check grouped and advanced
>>>
>>> 9. uncheck USE_FIELD3D and USE_JASPER (and USE_QT if only building the
>>> library)
>>>
>>> 10. Set the THIRD_PARTY_TOOLS_HOME environment variable to the directory
>>> where are stored unpacked external libraries (for example,
>>> R:\libraries\OpenImageIO\external\dist\win64). You can add variables by
>>> clicking Add entry button.
>>>
>>> 11. Though we set the THIRD_PARTY_TOOLS_HOME variable most packages will
>>> not be found automatically, because different library versions are
>>> hardcoded in cmake files. This means that you have to provide all paths
>>> manually :(
>>>
>>> 12. In CMAKE_CXX_FLAGS and CMAKE_C_FLAGS change /W3 to /W0 (get rid of all
>>> the warnings) and add /MP (multithreaded build)
>>>
>>> 12. Hit the Configure button. Cmake should automatically find externals
>>> libraries and prepare environment for creating the OIIO project. If the
>>> configuration process ends without errors go to next step.
>>>
>>> 13. There may be warnings in the cmake console, just ignore them
>>>
>>> 14. Hit the Generate button. Cmake will build a Visual Studio solution in
>>> the build directory.
>>>
>>> 15. Open the solution and select the release 64 bit configuration
>>>
>>> 16. To get startet, build only the OpenImageIO project. A linker error
>>> concerning tbb will come up. Currently cmake does not set the lib path
>>> correctly, so you have to add it yourself in the Properties Panel:
>>> Linker> Input> Additional Dependencies: add
>>> R:\libraries\OpenImageIO\external\dist\win64\tbb30_20110427oss\lib\tbb.lib
>>> (for Release, tbb_debug.lib for Debug build)
>>> It is the same for the maketx project
>>>
>>>
>>> Notes on building the dependencies yourself, which I really recommend to
>>> understand whats going on:
>>>
>>> zlib:
>>> use the visual studio files in zlib-1.2.5\contrib\vstudio or cmake
>>>
>>> glew:
>>> use the vc6 setup in glew-1.6.0\build\vc6
>>> for details read README/txt
>>>
>>> IlmBase:
>>> Use VS solution from latest CVS in IlmBase\vc\vc9\IlmBase
>>> for details on the expected folder structure read README.win32
>>>
>>> Openexr:
>>> use VS solution from latest CVS in OpenEXR\vc\vc8\OpenEXR
>>> for details on the expected folder structure read README.win32
>>>
>>> libjpg:
>>> in the VS Command Prompt type (the type of prompt determines which build
>>> environment and VS version to use: x86/x64)
>>> nmake /f makefile.vc setup-vc6 (only needed if you got a completely new
>>> download)
>>> nmake /f makefile.vc to build
>>> for details see install.txt
>>>
>>> libpng:
>>> use cmake to create a solution file, or use the vs solution in
>>> \projects\visualc71
>>> zlib must be compiled before this
>>> for details see INSTALL
>>>
>>> libtiff:
>>> edit JPEGDIR, ZLIBDIR, ZLIB_LIB in nmake.opt to match your paths (use
>>> forward slashes!)
>>> in the VS Command Prompt type:
>>> nmake /f makefile.vc libtiff
>>> for details, see: /html/build.html
>>>
>>> libjasper:
>>> does currently not work with 64 bit
>>> use the vc solution in \src\msvc
>>> see doc\jasper.pdf for details
>>>
>>>
>>> Cheers
>>>
>>> Sebastian
>>>
>>> On 09/20/2011 01:45 PM, Simon Eves wrote:
>>>> Hi there.
>>>>
>>>> Thanks so much for this. After 15 years in VFX myself I know how it goes!
>>>> :)
>>>>
>>>> Please let me know if there's any way I can help. I'd be more than happy
>>>> to do my own builds if you can guide me, or post whatever project files,
>>>> especially as we really need more than one flavor (2008 and 2010)... :(
>>>>
>>>> As for Boost, do you know about the pre-compiled versions available at
>>>> http://boost.teeks99.com (or something like that... it's 4:45am)
>>>>
>>>> Simon
>>>>
>>>> On Sep 20, 2011, at 12:17 AM, Sebastian Elsner<[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Simon,
>>>>>
>>>>> sorry for the delay I have been swamped with work. This week I have to
>>>>> recompile some of the dependencies because something went wrong with
>>>>> Boost. Hopefully I can then post them (we haven't even used the 64bit
>>>>> till now because of this).
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>> On 09/20/2011 05:38 AM, Simon Eves wrote:
>>>>>> Dear List,
>>>>>>
>>>>>> Apologies if I've missed the memo, but I'm just wondering if there has
>>>>>> been any progress in making OIIO compile cleanly and easily on Windows
>>>>>> x64, please?
>>>>>>
>>>>>> Several months ago, I was able to do a 32-bit build using the
>>>>>> pre-compiled external libraries package.
>>>>>>
>>>>>> One person was kind enough to send me a CMake script to do that
>>>>>> compilation myself, but I could not make it work for x64 either.
>>>>>>
>>>>>> There have been threads come and gone over the last two years
>>>>>> discussing this with no real conclusion.
>>>>>>
>>>>>> At least one person offered to publish his efforts in creating a
>>>>>> version of the external libraries package compiled for x64, but this
>>>>>> has never appeared (or if it did, I missed it...)
>>>>>>
>>>>>> I know full well that several people have solved this, if only for the
>>>>>> purposes of their own commercial products, so I guess it's
>>>>>> understandable if they don't want to share, but I guess I was hoping
>>>>>> for more from what is supposed to be an open project.
>>>>>>
>>>>>> I have been using OIIO happily on Linux for several months, and for
>>>>>> Mac more recently, both with no issues at all, and I *love* it!
>>>>>>
>>>>>> Why is Windows still such the red-headed step-child? :(
>>>>>>
>>>>>> Yours hopefully,
>>>>>>
>>>>>> Simon
>>>>>> _______________________________________________
>>>>>> Oiio-dev mailing list
>>>>>> [email protected]
>>>>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>>>>> _______________________________________________
>>>>> Oiio-dev mailing list
>>>>> [email protected]
>>>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>>> _______________________________________________
>>> Oiio-dev mailing list
>>> [email protected]
>>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>> --
>> Larry Gritz
>> [email protected]
>>
>>
>> _______________________________________________
>> Oiio-dev mailing list
>> [email protected]
>> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
