Yes, cmake is difficult to handle sometimes. But some people (like me)
never create visual studio solutions, because we don't own VS. WinSDK +
cmake (NMake target) is totally Ok for me.
Cmake is here, it does its job, just needs a few fixes.
I do not really like the idea of a permanent windows branch (if that was
what Piotr was saying). I am ok with a windows branch collecting
everything for merge into master.
On 06/17/2014 05:05 PM, Michel Lerenard wrote:
On 06/17/2014 04:37 PM, Nick wrote:
For quite a while we maintained vcproj's for EXR - that works but you
end up needing to keep old copies of visual studio around to make
sure that it builds for 2008, 2010, 2012, ...., and then you need to
run regressions on every variant to make sure nothing broke. It gets
really time consuming. I think the same argument would hold for
xcodeproj files.
As far as I know, the same argument is applied when using CMake: at
some point you have to compile the source and use Visual.
As I see it, no maintainer today is able to check all versions of the
compilers, with or without CMake.
CMake solves nothing but adds a layer of complexity because
configuring is neither trivial nor intuitive.
_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel
_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel
