This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
May Guile modules that are produced partly with the help of SWIG be put under GPL or LGPL? Swig itself is under a BSD-type license, as already J. Blandy pointed out. Similar as in the case of lexical scanners and parser generators, it makes sense to require that the input files of Swig should be part of the complete source code . And unlike lexical scanners or parser generators, swig is nowhere near of being considered as system component. So it might bite with the GPL/LGPL. I asked on the swig-list already, and Beazley did not object. But neither does Troll tech when it concerns KDE ... I use SWIG to export ncurses to guile. Part of it works, but the gaps are still huge, especially when it comes to videoattributes. (SWIG can easily work with user-defined data-types that are only referred to via pointers.) And its not clear how to protect stdscr and windows from garbage collection that contain yet subwindows. Deleting windows in a ncurses applications on which others depend causes seg.faults. Klaus Schilling