>> while that's not a fail as written, just an output message, about the first >> thing >> tried - building googletest - fails. I'll try to get to the bottom of it >> later, I'm >> being told I'm supposed to go have a weekend :) >> > > Interesting, I had not noticed that. Tonny on my team who brought this up to > me successfully built IoTivity for Linux 32-bit with this patch (at least I > believe he used the exact same patch). I'll see if we can investigate this on > our side too. I would expect that if all dependencies are correctly > installed, this should just be a warning message but things should still > build correctly. > > Outside of the Tizen build scripts/examples, there is another place where > 'default_arch' is set to platform.machine() and that's in: > https://github.com/iotivity/iotivity/blob/master/resource/csdk/connectivity/build/SConscript. > That file in fact duplicates some of what's already in > https://github.com/iotivity/iotivity/blob/master/build_common/SConscript. It > has its own version of 'os_arch_map' and 'host_target_map' tables for > example. I haven't looked at it in details but I suspect this is unnecessary > and hence sub-optimal.
Yes, there are some places where people appear to have duplicated a whole bunch more stuff than needed in setting up a new directory. Since I started working on the build scripts, that's an area I've left alone "until something breaks". Let me investigate further why it didn't build for me (I tried on a Ubuntu 16.04 VM). For now I can get a patch started in the review system, since clearly something needs to happen here. _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
