[Libssh] Staticaly linked and still require DLL?

[Aris Adamantiadis]

Could you add some kind of notice in the installer that states the legal
implication of distributing binaries including LGPL staticaly code ?
i.e. if your software is closed and distributed, it is not acceptable to
distribute only staticaly linked binaries (you must provide binaries
dynamically linked with libssh dll).

Licencing may evolve to a BSDv2 kind of licencing when I've got more
feedback of current and previous libssh contributors.

Aris
Andreas Schneider a écrit :
> On Wednesday 25 March 2009 15:26:04 Keisial wrote:
>   
>> Yes, gcc is a bit picky with it. libssh needs winsock, and also libeay32
>> or libssl, so winsock must appear after them.
>>
>>     
>
> Ok, so on windows you want a static library. I could build one and add it to 
> the NSIS installer. I just need feedback what you guys want or what is 
> missing.
>
> I'm not a windows developer nor a user. So tell me what you need or want.
>
>
> Cheers,
>
> 	-- andreas
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Libssh mailing list
> Libssh at cerkinfo.be
> http://www.cerkinfo.be/cgi-bin/mailman/listinfo/libssh
>