It seems I totally forgot to check the license on gnulib. The licensing situation is quite weird. Apparently, each gnulib "module" is licensed individually, and that license is determined by a file in the modules/ directory, not by the source file headers (which usually say GPL). Most of these modules are actually LGPL licensed. I was thinking that in order to make the licensing implications more obvious and make the LGPL easier to implement, I would diverge even further from the library's intended use by building a gnulib dll for each possible license.
I'm also writing a COPKG/README file explaining the intended (by me, not the FSF) usage and including recommendations regarding missing functions. The solution isn't always "use gnulib". Some of these functions have implementations in MSVC that are easy to get to. In one case, I was able to avoid it completely by including io.h instead of unistd.h. I think this change will improve the usability as well. Now all you need to do is make a config.h file (there will be an existing one you can use as a template), add an include path, and link some .lib files if there are missing symbols (the README file will say which). The linked .lib files will tell you what licenses you're bringing in. If all goes well, I'll have this pushed later this evening. _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
