[nanomsg] Re: Release packaging and build systems
- From: mike@xxxxxxxxxxxxx
- To: nanomsg@xxxxxxxxxxxxx
- Date: Tue, 23 Jul 2013 09:21:06 -0400 (EDT)
I am also for dropping the compatibility layer and keeping the code and API as
clean as possible.
-----Original Message-----
From: "Martin Sustrik" <sustrik@xxxxxxxxxx>
Sent: Tuesday, July 23, 2013 8:40am
To: nanomsg@xxxxxxxxxxxxx
Cc: "luca barbato" <luca.barbato@xxxxxxxxx>
Subject: [nanomsg] Re: Release packaging and build systems
On 23/07/13 12:52, luca barbato wrote:
>> I feel that we've hit the same problem as with ZeroMQ.
>>
>> Back then there was autotools build system, which didn't offer a way to
>> build the library on Windows. So we had to have separate MSVC projects.
>
> I build VLC and Libav for windows using mingw64 just fine, so it isn't
> strictly a problem.
>
> VLC is using autotools, Libav uses a custom pure sh+make build system.
>
> The problem you had was probably due some constraints that makes
> building C++ projects on window require picking either mingw64 for
> everything or msvc for everything.
>
> C projects do not have the problem, even if in order to use some
> microsoft tools you might want or even need to build everything using
> msvc (and that might require you to go through the hoops of
> c99toc98[1])
The problem is that Win devs work with MSVC. Asking them to use MinGW is
not realistic.
Martin
Other related posts:
