HAE team members, Those headers are not included in the distribution because there are not public APIs (i.e. they are only meant to be used by Core itself). As I see it the HAE has two options:
1) (same as 1 below) refactor to remove the dependencies on these projects a. I recognize this may be an issue given the current timelines 2) For the 16.04 release require the source of Core to be included to use this release AND plan on removing this dependency either in a 16.04.00a release, or a 16.10 release. It is not feasible for the Core team to expand our existing API surface. Especially in 16.04 as that release has shipped, and even in the 16.10 time frame we cannot commit to supporting such an increase in scope. From: [email protected] [mailto:[email protected]] On Behalf Of seungchul.han Sent: Tuesday, June 21, 2016 10:34 PM To: [email protected]; [email protected] Cc: [email protected] Subject: [Allseen-core] FW: [Allseen-hae] Building HAE independently of AllJoyn source code Dear all, The HAE project has some problem for building sources codes independently. Please refer to a mail below about details. I think option 2 is better than option 1, because we have to change a lot of codes in order to remove all dependencies on qcc lib. If we choose option 1, it could be a hard task against deadline of first release. So I'd like to ask CoreWG members about this issue. Could you update common/SConscript like attached patch-set? If it's possible, which version could be the best candidate version? (The HAE project has been developed based on v16.04.) If not, let us know your opinion about this issue. Your help will be greatly appreciated. Best Regards, Seungchul. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Thursday, June 16, 2016 10:12 PM To: [email protected]<mailto:[email protected]> Subject: [Allseen-hae] Building HAE independently of AllJoyn source code Dear all, Currently, to build HAE, we need to have the source code of AllJoyn Core as well as the source code of AllJoyn HAE. AllJoyn Core should be located inside a specific directory (../../alljoyn/core). It would be nice to remove this dependency as since 16.04 we can build AllJoyn base services (onboarding, notification and controlpanel) independently of Alljoyn Core through the ALLJOYN_DISTDIR scons variable. To break this dependency, I tried to update HAE by adding a build_core directory inside the HAE project and updating slightly the SConstruct to replace the inclusion of ../../core/alljoyn/build_core/SConscript by ./build_core/SConscript (as it was done in AllJoyn Onboarding base service: https://git.allseenalliance.org/cgit/services/base.git/tree/onboarding/SConstruct). However, when compiling HAE using ALLJOYN_DISTDIR, the compilation fails because HAE source code uses some internal headers from AllJoyn Core which are not copied into AllJoyn dist directory. Those files are: - qcc/SmartPointer.h (used in DeviceInfo.h) - qcc/StringSource.h (used in cpp/src/HaeAboutData.cc and cpp/samples/DeviceEmulator/ConfigLoader.cc) - qcc/Event.h (used in cpp/unit/unit_test/DUT/HaeTest.h) - qcc/Util.h (used in most source files) This is an issue, as because of this, we're unable to build HAE without the source code of AllJoyn Core which will prevent the "clean" integration of HAE into some build systems like buildroot or openwrt. So, there is two options, - Remove the dependencies on those files from HAE source code - Update common/SConscript from AllJoyn Core to install the files used by HAE in qcc dist directory however this will draw a lot of dependencies (see attached file), for example: - qcc/Event.h depends on qcc/posix/Event.h - qcc/StringSource.h depends on qcc/Stream.h which depends on qcc/Socket.h ... What do you think of this issue perhaps you should seek advice from the TSC? Best Regards, Fabrice _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
