Wed May 20 12:35:47 CEST 2015
I will have to try again, I was not able to make it work yesterday.
On 05/20/2015 01:30 PM, Dan Gudmundsson wrote:
> Does not cygwin still produce executables that depend on cygwin.dll,
> i.e. non native windows programs
> that will not work if you do not have cygwin (I know you can
> crosscompile with mingw compilers but that does not make
> it easier).
> I have ditched cygwin since long ago, and I prefer mingw and msys, it
> works and you can use Microsoft compiler or mingw compilers.
> rebar works and even erlang.mk <http://erlang.mk> worked as far as I
> tried it.
> IMO cygwin is a rabbit hole, do not go there it just makes it worse.
> On Wed, May 20, 2015 at 12:05 PM Loïc Hoguin <
> <mailto:>> wrote:
> On 05/20/2015 12:58 PM, Jani Hakala wrote:
> > Loïc Hoguin < <mailto:>> writes:
> >> Now Erlang compiles on Cygwin... but produces the win32 target.
> >> brings me to the main subject of this email: what would it
> involve to
> >> make Erlang work on Cygwin? Considering Cygwin is a mix of
> Windows and
> >> Linux it's probably just about enabling one or another piece of
> >> or is it?
> > Cygwin API Licensing Terms (https://cygwin.com/licensing.html)
> might be
> > an issue. Is linking to cygwin.dll required, and if yes, is it
> > to load only NIFs and port drivers that are distributed with a
> > that satisfies the Open Source Definition?
> > I think GPLv3 cygwin.dll license could be one the top reasons why
> > windows developers stay away from cygwin.
> This is largely a non-issue.
> The GPL only applies if you distribute the source code and/or the
> resulting build that links to Cygwin.
> The use case I am trying to improve is providing a development
> environment for people who deploy to Linux servers. Cygwin is not part
> of the resulting software.
> See my email to Jose Valim for more details.
> Loïc Hoguin
> erlang-questions mailing list
More information about the erlang-questions