Subject: Re: [dev] IoTivity in OpenWrt with build variables from environment
>
> On 06/18/2015 08:38 AM, Thiago Macieira wrote:
> > On Thursday 18 June 2015 13:40:58 Hauke.Mehrtens at lantiq.com wrote:
> >> What is the opinion on adding some option where IoTivity does not do it
On 06/18/2015 08:38 AM, Thiago Macieira wrote:
> On Thursday 18 June 2015 13:40:58 Hauke.Mehrtens at lantiq.com wrote:
>> 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 outsi
Hauke
-Original Message-
From: iotivity-dev-bounces at lists.iotivity.org
[mailto:iotivity-dev-boun...@lists.iotivity.org] 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 envir
On Thursday 18 June 2015 13:40:58 Hauke.Mehrtens at lantiq.com wrote:
> 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.
My opinion is th
lists.iotivity.org
> > [mailto:iotivity-dev-bounces at lists.iotivity.org] On Behalf Of
> > Hauke.Mehrtens at lantiq.com
> > Sent: Tuesday, June 09, 2015 4:07 PM
> > To: iotivity-dev at lists.iotivity.org
> > Subject: [dev] IoTivity in OpenWrt with build variables from
&
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 distributio
ot, it should be better to put the custom config in a script and load it
> from some proper place When build for Openwrt.
>
> Regards,
> Caiwen
>
> > -Original Message-
> > From: iotivity-dev-bounces at lists.iotivity.org
> > [mailto:iotivity-dev-bounces
y.org] On Behalf Of
> Hauke.Mehrtens at lantiq.com
> Sent: Tuesday, June 09, 2015 4:07 PM
> To: iotivity-dev at lists.iotivity.org
> Subject: [dev] IoTivity in OpenWrt with build variables from
> environment
>
> We want to use IoTivity on MIPS CPUs running in big endian mode with
> Subject: [dev] IoTivity in OpenWrt with build variables from environment
>
> We want to use IoTivity on MIPS CPUs running in big endian mode with
> OpenWrt as the Linux distribution. It would be nice to make it possible to
> add IoTivity to mainline OpenWrt, it supports many CPU
On Tuesday 09 June 2015 08:06:50 Hauke.Mehrtens at lantiq.com wrote:
> We want to use IoTivity on MIPS CPUs running in big endian mode with OpenWrt
> as the Linux distribution. It would be nice to make it possible to add
> IoTivity to mainline OpenWrt, it supports many CPU architectures. Currently
We want to use IoTivity on MIPS CPUs running in big endian mode with OpenWrt as
the Linux distribution. It would be nice to make it possible to add IoTivity to
mainline OpenWrt, it supports many CPU architectures.
Currently the scons build systems sets all the parameters for gcc and so on by
its
11 matches
Mail list logo
