[Haskell] Licensing problem, caused by static linking on windows

Alastair Reid alastair at reid-hoffmann.net
Fri Jul 2 13:22:08 EDT 2004

IANAL but my take on this is:

> 	Accompany the work with the complete corresponding
> machine-readable source code for the Library including whatever changes
> were used in the work (which must be distributed under Sections 1 and 2
> above); 

Including a pointer to a GHC tarfile or CVS tree seems like an easy way to 
accomplish this.

> and, if the work is an executable linked with the Library, with 
> the complete machine-readable "work that uses the Library", as object
> code and/or source code, so that the user can modify the Library and
> then relink to produce a modified executable containing the modified
> Library.

Including a .o file for each module of your program would be one way to 
accomplish this.

Alastair Reid

More information about the Haskell mailing list