The current build structure clashes somewhat with scons (and other) conventions. In particular, site_scons/, site_scons/site_init.py, and site_scons/site_tools are expressly designed to manage the kind of stuff that is currently scattered about the codebase, such as build_common/iotivityconfig, build_common/external_libs.scons, tools/scons, etc.
I've pushed a draft changeset as a first step in moving to a more standardized structure: https://gerrit.iotivity.org/gerrit/#/c/8597/ I'm not really sure how drafts work. Do they not get the Jenkins treatment? Are they visible? Thanks, Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160610/af171e42/attachment.html>
