[m-users.] Closed source Mercury projects on Windows

Martin McDonough foolkingcrown at gmail.com
Sat May 26 13:49:03 AEST 2018


So I see that the runtime, stdlib, and some components that are compiled
into Mercury programs with certain options (trace, mdb stuff) is licensed
under the LGPL. But on Windows, mmc can't be compiled to produce shared
libraries and the runtime and stdlib can't be compiled as shared libraries.

This seems like a serious problem for distributing any close source (or
even simply non-GPL-compatible) program for Windows.

I'm wondering how this is normally handled? Is there an experimental way to
produce shared libraries on Windows? Can it be done with some older
release? What are the existing closed source programs written in Mercury
and distributed for Windows like Prince XML doing in this case?

I do see that there is a note in Copying.lib about negotiating a different
license. Is it reasonable to expect that someday at least the parts that
are automatically compiled into Mercury programs (like mer_rt) would be
under a license like "LGPL with static linking exception" that some
projects like FLTK use, maybe even only for Windows?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/users/attachments/20180525/c5feef0b/attachment.html>

More information about the users mailing list