On 03/01/18 23:44, Gregg Reynolds wrote: > > > On Wed, Jan 3, 2018 at 3:49 PM, Dave Thaler <dtha...@microsoft.com > <mailto:dtha...@microsoft.com>> wrote: > > Below > > > > *From:* Gregg Reynolds [mailto:d...@mobileink.com > <mailto:d...@mobileink.com>] > *Sent:* Tuesday, January 2, 2018 9:46 PM > *To:* Dave Thaler <dtha...@microsoft.com > <mailto:dtha...@microsoft.com>> > *Cc:* iotivity-dev <iotivity-dev@lists.iotivity.org > <mailto:iotivity-dev@lists.iotivity.org>> > *Subject:* Re: [dev] Proposed API guidelines > > > > > > > > On Aug 18, 2017 10:55 AM, "Dave Thaler via iotivity-dev" > <iotivity-dev@lists.iotivity.org > <mailto:iotivity-dev@lists.iotivity.org>> wrote: > > As the new API maintainer, here’s a set of proposed API > guidelines. > > Please review so and feedback can be incorporated before > making official guidelines. > > > > 1 APIs > to be copied/merged at: https://wiki.iotivity.org/api
(...) > > [DT] Currently, the “out/” directory that’s created by a build. > That’s where built files get placed. > > > Ok, so add "no other header files will be published to the build > directory" or similar. It's been a while since I looked by my > recollection is pretty much everything gets dumped into the "out/" dir > structure. > > Maybe it would be better to stipulate that the result of a build will > be some binaries in directory foo (e.g. lib/) and some (preferably > one) headers in directory bar (e.g. include/). Use scons install to create headers dir (/usr/include/iotivity or out/deploy if --prefix is not used) I fixed this feature in master, but it's still pending in 1.3-rel: https://gerrit.iotivity.org/gerrit/#/c/23413/ Regards -- mailto:philippe.co...@osg.samsung.com gpg:0x467094BC https://blogs.s-osg.org/author/pcoval/
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
