It seems I was wrong — the LGPL does indeed allow for proprietary projects to be linked in to LGPL licenced libraries. That’s good; it saves me the hassle of changing over the library licence.
The CDC bootloader has been sending me a little insane, with a bug somewhere that I can’t find. I’m now at University severely sleep deprived, but I think I have a lead on a way to find the problem’s source. So far manually sending AVR109 protocol commands to the bootloader via a serial terminal works fine, but AVRDUDE compains of a non-response after several commands are correctly issued and responded to. Joerg Wunsch helpfully pointed me to AVRDUDE’s super-debug mode via the -vvvv option, which should give me a list of all the issued commands and recieved responses so I can find the exact point of failure.
When this is finally done, the next point release of the library will be uploaded for general consumption.
May 3rd, 2008 at 8:56 am
I think the only possible detriment to the LGPL might be that it requires the “Corresponding Application Code” to be disclosed with redistribution.
IMO, in the context of an AVR-GCC project, that means at a minimum one would have to supply the “.o” object files corresponding to each of the proprietary modules in the application, along with instructions on how to re-link those .o files with a modified version of MyUSB library to produce a new version of the combined work, along with instructions on how to go about loading the combined work on the intended target hardware.
I haven’t decided yet whether or not that would affect my willingness to use the library.