On 02/09/2015 01:41 PM, Thiago Macieira wrote: > On Monday 09 February 2015 13:36:53 Keane, Erich wrote: >> On Mon, 2015-02-09 at 13:32 -0800, Thiago Macieira wrote: >> >>> On Monday 09 February 2015 13:30:02 Keane, Erich wrote: >>> [SNIP] >>>> >>>> Unsure, but It looks like: >>>> <root>/service/<program name>/sdk/inc/<program name>.h >>> Hi Erich >>> >>> That's not what I meant. >>> >>> I am asking what the user should write in the #include line when including >>> the > API. Let's start from there before we decide where the files >>> reside. >> >> My apologies. At the moment, it would just be ocstack.h, OCApi.h, and >> <program name>.h, but you'd be expected to properly set the -I directory >> in your make file. > > Understood. > > Can we answer then what we'd like them to be?
>From some of my experience, using #include "iotivity/ocstack.h" #include "iotivity/Api.h" is better than #include "iotivity/ocstack.h" #include "iotivity/OCApi.h" It can help with setting up different libraries with minimal -I complexity. It also helps proof against filename collisions when developers use other libraries in addition to IoTivity. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com
