>From these four files. resource/csdk/connectivity/api/cautilinterface.h is need to be open public. But, this also requires resource/csdk/connectivity/api/cacommon.h
Other links is not required. resource/csdk/connectivity/api/cainterface.h resource/csdk/connectivity/api/casecurityinterface.h fix not to use below in cacommon.h looks required #ifdef HAVE_SYS_POLL_H #ifdef HAVE_WINSOCK2_H BR, Uze Choi -----Original Message----- From: Mats Wichmann [mailto:[email protected]] Sent: Friday, April 14, 2017 2:16 AM To: ??? (Uze Choi); iotivity-dev at lists.iotivity.org Subject: Re: [dev] still trying to figure out API docs - octimer.h On 04/13/2017 12:29 AM, ??? (Uze Choi) wrote: > The resource/csdk/connectivity files are public open purpose. > There was a discussion as below thru mailing list for this 3 weeks > before with Jiwhan.Seo. > > ------------------------------------------ > Since there were so many requirements to handle CA layer in person. > I believe that this header can be helpped for lots of scenarios. > please refer below the patchset > https://gerrit.iotivity.org/gerrit/#/c/18157/ > ---------------------------------- > > BR, Uze Choi Okay, circled back to check a bit more. Uze says the files in csdk/connectivity should be open, presumably meaning the four headers that are currently listed in the Doxyfile resource/csdk/connectivity/api/cacommon.h resource/csdk/connectivity/api/cainterface.h resource/csdk/connectivity/api/casecurityinterface.h resource/csdk/connectivity/api/cautilinterface.h None of these files are copied to out/, however, so that should probably be corrected. Among the files which ARE copied to out/, it's not a completely self-contained set: ocpayload.h includes securevirtualresourcetypes.h, which is a file not copied to out/ (this is a file that does appear in the c-api Doxyfile). That file in turn includes byte_array.h, which is neither copied to out/ nor listed in the c-api Doxyfile. One of the connectivity headers above also includes this byte_array.h. octypes.h includes iotivity_config.h which there was some discussion on recently (I think there was a patch that tried to reduce inclusion of this header), and it's somewhat problematic to include as a "published" header since it's designed to change based on doing checks on the build host. What should we do next to sort this out?
