As far as I can see there are a number of options: 1) Looking closer, RCSlib is LGPL so I can safely use it. However the header files that define the data types are GPL2 which means I can't use them directly. Assuming the data types haven't changed since EMC1 then I could use the public domain EMC1 header files.
2) Convince the authors of the affected header files to change the license to LGPL. The source files can still be GPL2 with LGPL headers. This has a number of political considerations and affects quite a few header files. 3) Use the Telnet application. Assuming there isn't too much overhead this bypasses the GPL issues completely. 4) SheetCam's plugin interface is structured so it can be used over a network, pipe or any other communications interface. Therefore plugins could be written that run in their own memory space and aren't directly linked to SheetCam. The relevant plugin headers and source files would have to be released under the LGPL or a modified GPL (allowing linking to SheetCam when not used in conjunction with GPL code). This isn't a problem. This solution would have a lower overhead than option 3 but I don't know how much of a difference it would make in practice. 5) If the Telnet option adds too much overhead then modify it to use binary protocol rather than a text based protocol. I suppose I need to do some testing and see how had I can push the Telnet interface. I want to stay legal without annoying the EMC developers. This is not worth getting into a fight over. Les ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
