To all, The introduction of glib has complicated the stack in a number of ways from licensing to OS support and beyond.
In the future, do not draw in additional libraries into Iotivity without vetting it in this forum. I plan to remove the glib dependency from iotivity for several reasons: 1) IANAL, but the license has viral requirements including the fact that a dynamically linked LGPL library must be replaceable which is a problem for RTOSes and linux-based devices TVs and Access Points. 2) Glib support on iOS (not directly supported), OSX and Windows (requires MSYS) is problematic 3) It is my understanding that we are only using glib for threads and mutex. This is a lot to pull into iotivity for only two features. Before I make this official, I would like to understand any reason that glib should be kept. Are we using glib for anything other than threads and mutexes? Pat Patrick Lankswert Intel Corporation Platform Engineering Group (PEG) / Communications and Devices Group (CDG) Engineering Manager Louisville, KY, USA -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150414/e165fc2b/attachment.p7s>
