On Tuesday 14 April 2015 18:45:30 Lankswert, Patrick wrote: > 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.
Correct. It's not difficult for dynamic linking, since replacing is as easy as recompiling glib from sources. We have no requirement to provide installation instructions (the "TiVo clause" from GPLv3). But for static linking, which is what will end up being used on devices with 2 MB of flash or less, it's a problem. > 2) Glib support on iOS (not directly supported), OSX and Windows (requires > MSYS) is problematic Right. > 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? See Ossama's email. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
