What is the opinion on adding some option where IoTivity does not do its architecture specific changes to CPPFLAGS and similar flags? In this mode someone from the outside has to provide these information. In this mode IoTivity would not fail if it was compiled against an unknown CPU architecture, but just assume that the caller knows what he does and provides the correct information. This would also allow the caller to change the compiler optimization levels or use a different compiler than gcc.
Currently I am thinking about something like this: Adding an option to the build scripts like USE_ENV=true If this is set the complete environment will be provided to the called gcc process and other processors called by the scons build system by the build system. The user can specify its own compiler name and flags from the outside. The arch will be not checked against os_arch_map The CPU specific changes in build_common/linux/SConscript will not be done Probably something more. ;-) Currently I would only target Linux. This would help OpenWrt, but I assume also some others Linux users will benefit from this, like other Linux distributions. Are there any plans for integration into Debian, Fedora or any other Linux distribution? >From my opinion these changes would only affect some build files, I do not >want to add support for other compilers for example. I am just writing this to check if this would be acceptable before I start to implement this. Hauke -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Dienstag, 16. Juni 2015 16:24 To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity in OpenWrt with build variables from environment On Thursday 11 June 2015 01:47:40 Zhang, Caiwen wrote: > The ideal way is to split OpenWrt from linux like Tizen. In the > OpenWrt specific Script(build_common/openwrt/SConscript) list the CFLAGS > cases. I disagree with that. OpenWRT should be regular Linux, since that's how most Linux distributions (including Yocto-based ones) will build IoTivity. If Tizen requires different options, so be it, but the regular Linux ones should not suffer for it. Please work with Hauke so that the OpenWRT builds work fine. See also Kevron's emails about building with Yocto. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
