[nanomsg] Re: Release packaging and build systems
- From: luca barbato <luca.barbato@xxxxxxxxx>
- To: Martin Sustrik <sustrik@xxxxxxxxxx>
- Date: Tue, 23 Jul 2013 15:10:47 +0200
On Tue, Jul 23, 2013 at 2:40 PM, Martin Sustrik <sustrik@xxxxxxxxxx> wrote:
> 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.
There are 2 problems, one is if you have contributor using only msvc
and wanting to touch only system native tools,
that is a near impossible solution. Relaxing it so they can have a
generator for a msvc project is simple, cmake can do that
out of box, but then they must learn cmake and update it from their
msvc changes.
The other is _usage_ on windows. In that case as long there is a
windows build with debug symbols and headers they are happy.
The second is easy to achieve with both build systems and actually
easier with autotools.
lu
Other related posts:
