Keith MARSHALL wrote:
>>If my memory serves me correctly, all stuff built on MSYS
>>get linked with a GPL'd library (MSYS) that handles
>>eg. the path transformations.
> This is my chance to tell you to go RTFM, (even though I
> consider it offensive and unnecessary, but you did it to me,
> and like the elephant, I don't forget such things).
> This stuff surely *is* documented somewhere -- I don't recall
> exactly where, (and I couldn't be bothered to go searching for
> it again), but I do recall having seen it in the past.
I see you didn't drive tip all the way in.
One of the points of telling someone to RTFM is also telling
where to find the information.
This can be found in MSYS_LICENSE.rtf if anyone cares.
It would be nice, though, if this information was available
on the web site. It is not nice to force people to download
the package in order to view the license.
> If you are building *native* Win32 apps, using MinGW, you are
> *not* linking against msys-1.0.dll, or any other GPL library,
> so you are not *obliged* to GPL your code, (although it would
> be nice if you did).
Ah, but what if it isn't my code and I don't feel like hosting
a mirror (in essence)?
Besides, I might want to use BSD license...
> If you are developing MSYS itself, and therefore linking
> against msys-1.0.dll, then you *are* linking with GPL code,
> (inherited from CygWin), and you must, therefore, GPL your
So just to be clear about this:
Without explicitly telling the linker to link against msys-1.0.dll,
all building and linking done within MSYS shell using MSYS tools
is okay in that respect. And there is no implicit linking
done when building stuff using MSYS.
In that case, can you remember what was that about having
some environment variable (or something else?) that was used
to detect if executable was run in MSYS environment or not?
Was that about MSYS tools then?
... He's dead, Jim. You get his tricorder, I'll get his wallet.