Ossama,
I am not sure that your case justifies making glib a requirement for the entire stack on multi-threaded systems. Correct me if I am wrong, but this will only for linux which will have glib already installed. Pat From: Othman, Ossama [mailto:[email protected]] Sent: Tuesday, April 14, 2015 3:54 PM To: Lankswert, Patrick Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] glib Hi Pat, On Tue, Apr 14, 2015 at 11:45 AM, Lankswert, Patrick <patrick.lankswert at intel.com <mailto:patrick.lankswert at intel.com> > wrote: 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? I'm currently using GDbus <https://developer.gnome.org/gio/stable/gdbus-convenience.html> found in glib's GIO library to make D-Bus calls to BlueZ in my LInux BLE GATT transport work. Since IoTivity was already using glib, GDBus seemed like the best way to go. -Ossama -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150414/f0db879d/attachment.html> -------------- 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/f0db879d/attachment.p7s>
