On Sun, Nov 20, 2011 at 5:20 PM, Stuart Webster <sw_webs...@hotmail.com> wrote: > That's basically what these patches provide. 32-bit configurations build > free of warnings with /W3. 64-bit configurations generate several legitimate > "conversion from 'size_t' to 'int', possible loss of data" warnings which I > intend to address with a subsequent patch. Note that this patch does not > remove the MSVC9 project files, but I appreciate that maintaining both sets > is not an appealing prospect. I would suggest that they are removed if this > patch or some variant thereof is accepted.
Hi, having to maintain multiple sets of Windows build files is the problem indeed. It seems like for each iteration of Visual Studio we need to create another set of project files as the conversion doesn't seem to work as expected (at least import library location is lost during conversion). This is the reason why something like CMake as an abstraction would be a lot more appealing. As far as I understand it's possible to generate Visual Studio project files using CMake. If this works well nothing would prevent us from distributing the project files separately. Does this sound acceptable? I don't think we can drop MSVC9 support in the middle 2.1 cycle as this would be a major backwards compatibility break. -- Mikko Koppanen _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
