On Tue, Jan 27, 2015 at 7:15 PM, Thiago Macieira <thiago.macieira at intel.com> wrote: > On Tuesday 27 January 2015 14:01:06 Lankswert, Patrick wrote: >> That is a good point. The naming convention should reflect the open source >> project and not necessarily the consortium. > > Here's another idea: let's just use "iot" for C++ namespace, for include path > (/usr/include/iot/*) and for C prefix. > > It's not unprecedented: ICU claimed /usr/include/unicode/* and GtkWebKit > claimed libwebkit.so.
Hi Well what about several implementation of iot ? will the definitions match ? Anyway let me also suggest to also use /usr/include/iotivity/ for useful headers (out of standard or not yet part of it) https://gerrit.iotivity.org/gerrit/261 I needed them to build an example on tizen (will document this soon) Later online -- xmpp:philippe.coval.pro at gmail.com https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/ .
