Only what we need to define is source directory structure and out directory header directory structure. Let debug one by one. This is initial proposal.... what should we change??
[IoTivity Source code] C ./resource/c_common/include <-- new proposal...(merged into single directory..) ./resource/csdk/include (octypes only...) ./resource/csdk/stack/include ./resource/csdk/security/include ./resource/csdk/security/provisioning/include ./resource/csdk/security/provisioning/include/oxm ./resource/csdk/security/provisioning/include/cloud ./resource/csdk/routing/include ./resource/csdk/resource-directory/include C++ ./resource/include (All C++ header) ./resource/csdk/include (octypes common to C API) [Out directory] C/C++ : lots of missing header file here... ./include/c_common ./include/resource BR, Uze Choi -----Original Message----- From: Dave Thaler [mailto:[email protected]] Sent: Tuesday, March 28, 2017 3:03 AM To: Mats Wichmann; Daniel Mihai; ??? (Uze Choi); 'Nash, George'; 'Philippe Coval'; iotivity-dev at lists.iotivity.org Subject: RE: [dev] [Iotivity-maintainers] C API docs: which Doxyfile? > From: Mats Wichmann > So I'm guessing in the short term only the "installed location" > question can reasonably be addressed. That is a single directory in > "out", but still split into a number of subdirs. Is that "good > enough" or is there more work to be done? Does anyone actually build against > the "out" tree? Yes. And I'm fine with Dan's recommendation. Dave
