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 [cut] > I created the attached patch 004-use-env.patch to use these environment > variables instead of the variables hard coded in the IoTivity build files. > In addition I had to allow the mips architecture with patch > 003-add-mips.patch. > > Is this the right approach or how should I handle it? I do not think adding > every option to the IoTivity build files will work, for example see -mtune > this will be different for many SoCs. I also would like to get such a patch > into upstream IoTivity so I do not have to take care of it manually. The > attached Makefile is the OpenWrt Makefile with all the IoTivity specific > options.
Hello Hauke Those are interesting contributions. The patches look simple enough and I don't expect problems in accepting them. In order for us to do so, we need you to submit them via the Gerrit infrastructure. Please see https://wiki.iotivity.org/how_to_use_gerrit. Note you'll need to modify your commit messages to include a Signed-off-by footer. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
