I havn't set a USE_SIMD flag, do you have a suggest on what to try.
Yes It breaks further on though. in simd_test I get,
its my end of day, and I was going to go at it tomorrow, but also I am
open to any advice.
simd_test.cpp
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(332): warning C4305:
'argument': truncation from 'int' to 'bool'
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(629): note: see
reference to function template instantiation 'void
test_shuffle<OpenImageIO::v1_7::simd::mask4>(void)' being compiled
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(333): warning C4305:
'argument': truncation from 'int' to 'bool'
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(334): warning C4305:
'argument': truncation from 'int' to 'bool'
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(335): warning C4305:
'argument': truncation from 'int' to 'bool'
s:\storage\git\oiio.git\src\include\openimageio\tinyformat.h(178):
error C2718: 'const OpenImageIO::v1_7::simd::int4': actual parameter
with requested alignment of 16 won't be aligned
s:\storage\git\oiio.git\src\include\openimageio\tinyformat.h(600):
note: see reference to class template instantiation
'tinyformat::detail::is_convertible<T,int>' being compiled
with
[
T=OpenImageIO::v1_7::simd::int4
]
s:\storage\git\oiio.git\src\include\openimageio\tinyformat.h(883):
note: see reference to function template instantiation 'void
tinyformat::detail::FormatIterator::accept<T1>(const T &)' being
compiled
with
[
T1=OpenImageIO::v1_7::simd::int4,
T=OpenImageIO::v1_7::simd::int4
]
s:\storage\git\oiio.git\src\include\openimageio\tinyformat.h(944):
note: see reference to function template instantiation 'void
tinyformat::detail::format<T1,T2>(tinyformat::detail::FormatIterator
&,const T1 &,const T2 &)' being compiled
with
[
T1=OpenImageIO::v1_7::simd::int4,
T2=OpenImageIO::v1_7::simd::int4
]
S:\storage\git\oiio.git\src\include\OpenImageIO/strutil.h(91): note:
see reference to function template instantiation 'void
tinyformat::format<T1,T2>(std::ostream &,const char *,const T1 &,const
T2 &)' being compiled
with
[
T1=OpenImageIO::v1_7::simd::int4,
T2=OpenImageIO::v1_7::simd::int4
]
S:\storage\git\oiio.git\src\libutil\simd_test.cpp(420): note: see
reference to function template instantiation 'std::string
OpenImageIO::v1_7::Strutil::format<OpenImageIO::v1_7::simd::int4,OpenImageIO::v1_7::simd::int4>(const
char *,const T1 &,const T2 &)' being compiled
with
[
T1=OpenImageIO::v1_7::simd::int4,
T2=OpenImageIO::v1_7::simd::int4
]
On 16 August 2016 at 19:50, Larry Gritz <[email protected]> wrote:
> Which USE_SIMD flags are you using, do you know?
>
> And, out of curiosity, if you change those two functions from
>
>> inline simd::float4 sRGB_to_linear (simd::float4 x)
>
> to
>
>> inline simd::float4 sRGB_to_linear (const simd::float4 &x)
>
> does that fix the warning?
>
>
>
>> On Aug 16, 2016, at 9:06 AM, Ben De Luca <[email protected]> wrote:
>>
>> I managed to build all the dependancies via script but now I have some
>> issues building
>>
>> src\include\openimageio\fmath.h(231): error C2719: 'a': formal
>> parameter with requested alignment of 16 won't be aligned
>> src\include\openimageio\fmath.h(231): error C2719: 'low': formal
>> parameter with requested alignment of 16 won't be aligned
>> src\include\openimageio\fmath.h(231): error C2719: 'high': formal
>> parameter with requested alignment of 16 won't be aligned
>> src\include\openimageio\fmath.h(229): error C2719: 'a': formal
>> parameter with requested alignment of 16 won't be aligned
>> src\include\openimageio\fmath.h(229): error C2719: 'low': formal
>> parameter with requested alignment of 16 won't be aligned
>> src\include\openimageio\fmath.h(229): error C2719: 'high': formal
>> parameter with requested alignment of 16 won't be aligned
>>
>> I think its meant to be like
>>
>> /// clamp a to bounds [low,high].
>> template <class T>
>> inline T
>> clamp (const T& a, const T& low, const T& high)
>> {
>> return (a < low) ? low : ((a > high) ? high : a);
>> }
>>
>>
>> // Specialization of clamp for float4
>> template<>
>> inline simd::float4
>> clamp (const simd::float4& a, const simd::float4& low, const simd::float4&
>> high)
>> {
>> return simd::min (high, simd::max (low, a));
>> }
>>
>> Which compiles at least, until I get to the simd tests.
>>
>> inline simd::float4 sRGB_to_linear (simd::float4 x)
>> and
>>
>> inline simd::float4 linear_to_sRGB (simd::float4 x)
>>
>> Also have the same problem
>>
>>
>>
>> On 16 August 2016 at 11:02, Sebastian Elsner | RISE
>> <[email protected]> wrote:
>>> There are still my (a bit outdated) windows build notes:
>>> http://piratepad.net/0rqEZFwrKg
>>>
>>>
>>> On 08/16/2016 09:25 AM, Larry Gritz wrote:
>>>
>>> Have you guys looked at the appveyor.yml file in the project? It contains a
>>> ghastly, but basically working, recipe for assembling most of the
>>> dependencies, enough to enable a build of OIIO. Presumably that should be a
>>> good starting point for making a more elegant script that will do it all. I
>>> would love to have that as a contribution.
>>>
>>> Also, anybody who wants to suggest specific edits to the INSTALL.md or the
>>> wiki instructions, I am all ears. But you've got to just give me the exact
>>> text and I'll replace it. You can't just say "fix it" because I don't know
>>> enough about Windows to get it right. You have to put the exact words in my
>>> mouth, so to speak.
>>>
>>>
>>>
>>> On Aug 15, 2016, at 3:50 PM, Ben De Luca <[email protected]> wrote:
>>>
>>> I have some scripts that I use for compiling on different platform , this
>>> and a few other big things, wraps cmake, autoconfig, qmake etc.
>>>
>>> Thanks, the cmake path seems to be the write one.
>>> libjpeg that compiles cleanly here with cmake,
>>> https://github.com/LuaDist/libjpeg
>>>
>>>
>>> Im only stuck with,
>>> libtiff, compiled the library, but breaks on one of the tools I don't
>>> actually need.
>>> boost - I have that working on linux and mac, just need to port my tool to
>>> call the windows bootstrap (which I assume exists)
>>> and tbb
>>>
>>> Are gtest and jasper necessary for building, or is it just testing?
>>>
>>> how do you build tbb? I havn't looked, just hoped that cmake might work.
>>>
>>> At the end I should have a script that you can give to a new install of
>>> windows/centos/ubuntu/osx10.7+ and it will build it all.
>>>
>>>
>>>
>>>
>>>
>>> On 16 August 2016 at 00:10, Thorsten Kaufmann
>>> <[email protected]> wrote:
>>>>
>>>> Yup, have not published anything, but can do so at least for all external
>>>> stuff i guess. I did some weird wrapping of the provided cmake setups to
>>>> allow switching compiler and platform toolset. This is only controllable on
>>>> the command line in cmake and the rez cmake integration does not yet
>>>> support
>>>> changing them afaik.
>>>>
>>>>
>>>> I have not yet done anything beyond wrapping the dependencies that already
>>>> had cmake setups though.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Thorsten
>>>>
>>>>
>>>> ---
>>>> Thorsten Kaufmann
>>>> Production Pipeline Architect
>>>>
>>>> Mackevision Medien Design GmbH
>>>> Forststraße 7
>>>> 70174 Stuttgart
>>>>
>>>> T +49 711 93 30 48 661
>>>> F +49 711 93 30 48 90
>>>> M +49 151 19 55 55 02
>>>>
>>>> [email protected]
>>>> www.mackevision.com
>>>>
>>>> Geschäftsführer: Armin Pohl, Joachim Lincke, Jens Pohl
>>>> HRB 243735 Amtsgericht Stuttgart
>>>>
>>>> ---
>>>> NEW PRODUCT: Innovation in moving images - Motionbox
>>>> VFX: Game of Thrones, Season 5 – VFX making of reel.
>>>> SOCIAL: Follow us on Facebook, Twitter, Behance and Vimeo
>>>>
>>>> ________________________________
>>>> Von: Oiio-dev <[email protected]> im Auftrag von Ben
>>>> De Luca <[email protected]>
>>>> Gesendet: Montag, 15. August 2016 22:54
>>>> An: OpenImageIO developers
>>>> Betreff: Re: [Oiio-dev] Windows build instructions?
>>>>
>>>> Is res the thing that came out of DrD? Did you publish what you have?
>>>>
>>>> I wrote my own thing whist I installed visual studio, oh pain.
>>>>
>>>>
>>>>
>>>> On 15 August 2016 at 22:41, Thorsten Kaufmann
>>>> <[email protected]> wrote:
>>>>>
>>>>> Hey there,
>>>>>
>>>>> I was going for windows here too recently and gave up after a while. I
>>>>> would prefer if we could have a joint effort to create proper build setups
>>>>> for the dependencies. Some come with CMake setups already and are easy
>>>>> targets. Quite some don't and it's even kind of obscure for some to be
>>>>> found
>>>>> due to weird windows port naming differences and whatnot.
>>>>>
>>>>> The reason i would prefer that way is that chances are the compiler
>>>>> chosen for the binary dependencies don't match what i need and i have to
>>>>> recompile anyways and even more so now that i actually maintain different
>>>>> versions (runtime versions vs. architecture vs. python version etc.) of
>>>>> most
>>>>> things i compile i would prefer not having to set that all up manually but
>>>>> simply rebuild as needed.
>>>>>
>>>>> Here's a list of the ones i managed to get built rather straight forward
>>>>> (the first version being the one in the externals, the second the one i
>>>>> built).
>>>>>
>>>>> glew 1.5.1 1.13.0
>>>>> ilmbase 1.0.1 2.2.0
>>>>> openexr 1.6.1 2.2.0
>>>>> libpng 1.2.3 1.6.23
>>>>> zlib 1.2.3 1.2.8
>>>>> tbb tbb21_200090511oss tbb44_20160526oss
>>>>>
>>>>> And here's the ones i am seeing issues with:
>>>>>
>>>>> gtest (1.3.0)
>>>>> jasper (1.900.1)
>>>>> jpeg (6b)
>>>>> openjpg (1.3)
>>>>> tiff (3.8.2)
>>>>>
>>>>>
>>>>> I wonder what the best way to tackle would be? On my end i am wrapping
>>>>> them all as rez packages, but that is hardly something to be useful to
>>>>> everyone. I am thinking standard cmake setups + rez wrappers as an
>>>>> additional repo, so one could also build without rez easily.
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Thorsten
>>>>>
>>>>>
>>>>>
>>>>> ________________________________________
>>>>>
>>>>> ---
>>>>> Thorsten Kaufmann
>>>>> Production Pipeline Architect
>>>>>
>>>>> Mackevision Medien Design GmbH
>>>>> Forststraße 7
>>>>> 70174 Stuttgart
>>>>>
>>>>> T +49 711 93 30 48 661
>>>>> F +49 711 93 30 48 90
>>>>> M +49 151 19 55 55 02
>>>>>
>>>>> [email protected]
>>>>> www.mackevision.com
>>>>>
>>>>> Geschäftsführer: Armin Pohl, Joachim Lincke, Jens Pohl
>>>>>
>>>>> HRB 243735 Amtsgericht Stuttgart Von: Oiio-dev
>>>>> <[email protected]> im Auftrag von Ben De Luca
>>>>> <[email protected]>
>>>>>
>>>>> Gesendet: Montag, 15. August 2016 19:27
>>>>> An: OpenImageIO developers
>>>>> Betreff: Re: [Oiio-dev] Windows build instructions?
>>>>>
>>>>>
>>>>> I see the openEXR version, is very old in the external libs, but that
>>>>> the windows build is compiling from link in docs.
>>>>> I wondered if you might share?
>>>>>
>>>>> -Ben
>>>>>
>>>>> On 15 August 2016 at 20:05, Ben De Luca <[email protected]> wrote:
>>>>>> Hi,
>>>>>> I was reading the documentation here,
>>>>>> https://sites.google.com/site/openimageio/building-oiio-on-windows
>>>>>> which is linked from the main site. Which seems to be pretty different
>>>>>> than whats in the repo install instructions.
>>>>>>
>>>>>> In the repo it says look for latest windows build instructions in the
>>>>>> wiki, but that page
>>>>>>
>>>>>> (http://openimageio.org/wiki/index.php?title=Building_OpenImageIO_on_Windows)
>>>>>> doesn't exist.
>>>>>>
>>>>>> In the notes, it says that the external project should be a sibling of
>>>>>> the trunk, but step 8 says some thing about setting
>>>>>> THIRD_PARTY_TOOLS_HOME, I looked in the cmake on master and there are
>>>>>> references lock files that don't appear to be in the external tools
>>>>>> windows zip.
>>>>>>
>>>>>> steps 5 and 6 seem to refer to the same thing, downloading boost but
>>>>>> the link to boost pro is dead now http://www.boostpro.com/download .
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>> --
>>>
>>> check out pointcloud9.com
>>>
>>> Sebastian Elsner - Pipeline Technical Director - RISE
>>>
>>> t: +49 30 20180300 [email protected]
>>> f: +49 30 61651074 www.risefx.com
>>>
>>> RISE FX GmbH
>>> Schlesische Straße 28, 10997 Berlin
>>> An der Schanz 1A, 50735 Köln
>>> Büchsenstraße 20, 70174 Stuttgart
>>> Gumpendorferstraße 55, 1060 Wien
>>> 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
>>>
>> _______________________________________________
>> 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
