On 04/11/2017 02:23 PM, Nash, George wrote:
> For the first error the fix is quite easy I have filed a Jira ticket for that 
> issue and will have a patch submitted shortly
> https://jira.iotivity.org/browse/IOT-2029
> I have not been able to reproduce the second issue.
> I have seen this type of issue when old build products are causing an error.
> Here are two things to try.
> 1st
> Do a clean build
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 -c
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1
> 
> If that does not work manually clean the build output and try again sometimes 
> the scons clean misses something that should have been cleaned and this 
> solves the problem. If you have another build linux or tizen this will wipe 
> out the build output for those OS if you may want to be more selective than 
> this. Sometimes just deleting the .sconsign.dblite file will fix the issue 
> but I normally just rebuild everything.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 ?c
> $> rm -fr out #delete the output directory
> $> rm .sconsign.dblite #delete scons?s database file that it uses for 
> tracking which files need a rebuild.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1


I should note the clean targets are relatively broken: scons isn't told
about everything that is built, because some of the things happen
outside defined scons "targets".  So not the fault of scons. Not sure if
that's enough to actually affect a subsequent build, that would take
research I haven't done, but manual cleaning may be a good idea. Recent
not-directly-related but possibly interesting example: I found out a
useful #define from iotivity_config.h was missing, because
iotivity_config.h in resource/c_common is not recreated if it exists,
and nothing ever removes it (it's not a "target", just the effect of
some statements in a file); my copy was six months old and another four
or so checks had been added since).


Reply via email to