Age | Commit message (Collapse) | Author |
|
Lot of simplification since "scons install"
is supported by upstream.
Note that 2.0.0 is in 1.4-rel branch
IoTivity extra files are now in /usr/lib*/iotivity/
Bug: https://jira.iotivity.org/browse/IOT-2998
Cc: yocto@yoctoproject.org
Origin: https://lists.iotivity.org/g/iotivity-dev/message/9943
Forwarded: https://lists.yoctoproject.org/pipermail/yocto/2018-September/042652.html
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Note that fail on warning flag has been added,
and can be used in .bbappend if needed after reporting bugs:
http://wiki.iotivity.org/report
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Since IoTivity-1.3.0
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Since IoTivity-1.3.0
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Note that SECURITY is now enabled but might cause issues on some examples.
Bug: https://jira.iotivity.org/browse/IOT-2651
Forwarded: https://lists.yoctoproject.org/pipermail/yocto/2018-January/039678.html
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Set RPATH to ORIGIN as supported by gcc/ld (-rpath=\$ORIGIN)
Observed issue on poky master was:
ld: warning: libconnectivity_abstraction.so, \
needed by out/yocto/x86_64/release/liboctbstack.so,
not found (try using -rpath or -rpath-link)
out/yocto/x86_64/release/liboctbstack.so: \
undefined reference to `coap_write_block_opt'
Note that problem is also about
to be fixed upstream directly in scons files.
Bug: https://jira.iotivity.org/browse/IOT-2651
Relate-to: https://gerrit.iotivity.org/gerrit/#/c/22355/
Thanks-to: Mikko Ylinen <mikko.ylinen@intel.com>
Forwarded: https://lists.yoctoproject.org/pipermail/yocto/2018-January/039677.html
Signed-off-by: Philippe Coval <philippe.coval@osg.samsung.com>
|
|
Reason is described in gcc7 porting notes:
"Several C++ Standard Library headers
have been changed to no longer include the
<functional> header.
As such, C++ programs that used components
defined in <functional> without explicitly
including that header will no longer compile."
It was tested on yocto poky master on iotivity-1.2.1 (and later)
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Removing trailing separator solved issues observed
on older version of yocto (daisy at least):
Parsing recipes..ERROR: ExpansionError during parsing
/recipes-core/iotivity/iotivity_1.2.0.bb:
Failure expanding variable do_fetch[file-checksums],
expression was ${@bb.fetch.get_checksum_file_list(d)}
which triggered exception ValueError:
need more than 1 value to unpack
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Removing trailing separator solved issues observed
on older version of yocto (daisy at least):
Parsing recipes..ERROR: ExpansionError during parsing
/recipes-core/iotivity/iotivity_1.2.0.bb:
Failure expanding variable do_fetch[file-checksums],
expression was ${@bb.fetch.get_checksum_file_list(d)}
which triggered exception ValueError:
need more than 1 value to unpack
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Removing trailing separator solved issues observed
on older version of yocto (daisy at least):
Parsing recipes..ERROR: ExpansionError during parsing
/recipes-core/iotivity/iotivity_1.2.0.bb:
Failure expanding variable do_fetch[file-checksums],
expression was ${@bb.fetch.get_checksum_file_list(d)}
which triggered exception ValueError:
need more than 1 value to unpack
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
It was discovered while building AGL using Intel BSP.
Also fixes a dangling syslink, which was discovered while
building Ostro OS.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Reapply patch that was in the iotivity 1.1-rel branch,
and (wrongly) removed in 1.2.0.
It had to be reintroduced in upstream 1.2-rel and as a patch
for 1.2.0. View upstream bug report at:
https://jira.iotivity.org/browse/IOT-1219
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Apply patch from iotivity-1.2.1:
* [PATCH 081/341] yocto: Add aarch64 for DragonBoard-410c
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* The build parameters are now aligned to upstream default.
* Compared to earlier recipes, configuration changes are:
- WITH_RD parameter now replaced by RD_MODE
(set to CLIENT by default)
- ROOTING was previously set to gateway (GW)
but now set to EP.
More details at: https://wiki.iotivity.org/yocto
* A workaround was needed to install tinycbor headers
required by iotivity headers (this has been fixed in 1.2-rel),
The problem was observed while building iotivity-node.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* linux: Support also armeabi-v7a TARGET_ARCH
* yocto: Add aarch64 for DragonBoard-410c
* minor changes
* Fix harmless typo in recipe
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
It was observed using tizen-distro with raspberrypi BSP layer
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* More arch support
* Import yocto PATH into scons env to use sysroot's tools
(pkg-config, gdbus-codegen, ...)
* Workaround mips support for hippomocks
Status of meta-oic's downstream patches:
* arch.patch : merged
https://gerrit.iotivity.org/gerrit/#/c/2873/
* gcc5.patch : merged
https://gerrit.iotivity.org/gerrit/#/c/7759/
* gcc6.patch : merged
https://gerrit.iotivity.org/gerrit/#/c/8651/
* hippomocks_mips_patch : open
https://github.com/dascandy/hippomocks/pull/50
* yocto_paths.patch : merged
https://gerrit.iotivity.org/gerrit/#/c/11899/
|
|
* Inspired from Kishen Maloor's iotivity_1.1.0.bb.
* Note this version of recipe
is using upstream's git repo as source
because it's better for upstream/downstream cooperation
More details at:
https://wiki.iotivity.org/yocto
* Update to upstream "1.1-rel" maintenance branch
- QA checks are fixed
to support Yocto jethro base and later,
without it packaging task will fail and report this message :
ERROR: QA Issue: No GNU_HASH in the elf binary
* Tinycobor is updated to v0.2.1.
* Gtest is now statically linked.
* Security is still not enabled,
but can be easly enabled with "SECURED=1" scons's flag.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Without this change and error on linkage is displayed :
ld: observer.o: undefined reference to symbol
'pthread_create@@GLIBC_2.2.5' libpthread.so.0: error adding
symbols: DSO missing from command line collect2: error: ld
returned 1 exit status
Also YOCTOLDFLAGS are replaced with regular LDFLAGS,
to use quality check.
Without this, QA check is failing and this message is reported:
do_package_qa: QA Issue: No GNU_HASH in the elf binary:
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
This has been tested with iotivity-1.1.1
but also applies to earlier versions.
Without this, QA check is failing and this message is reported:
do_package_qa: QA Issue: No GNU_HASH in the elf binary:
(...)
iotivity-simple-client/simpleclient' [ldflags]
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Patched service/resource-container/examples/BMISensorBundle/src/BMISensor.cpp
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Patched service/resource-container/src/BundleInfoInternal.cpp
to correctly initialize a boolean variable.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Produces builds with SECURE=0 by default. This would help
with initial ramp up and testing.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Added new recipe for the IoTivity 1.1.0 release.
* Update sample client recipe with newer client source.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Added new IoTivity recipe for building 1.0.1
resource and service components.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Modified layer.conf to ignore all .bbappend recipes
from recipes-kernel instead of using BBMASK to achieve
the same.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Incorporated the standlone plugin framework for non OIC protocols
along with the ZigBee/Telegesis wrappers, sample applications and
tests into the build.
* Removed unnecessary end-of-line whitespaces in the recipe.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Added recipe with packaged source code for the
OICSensorBoard application.
* Application description and set-up guidelines are in
https://wiki.iotivity.org/_media/oicsensorboardreadme.pdf
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Added new IoTivity recipe for building 1.0
resource and service components. Removed
older 0.9.2 recipe.
* Added separate source code patches for:
* Extending list of supported Yocto target
architectures in IoTivity's scons build.
* Passing Yocto's PKG_CONFIG.. settings to scons.
* Excluding the ZigBee plug-in in the Yocto build.
* Allowing hippomocks based unit tests to build on
a MIPS target.
* Updated source for the iotivity-simple-client recipe
sample.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Taken from iotivity master commit
ca25f608ed10f6c9b5adbdeadb74068f476a04c6
to address GCC5.0 and CLANG 3.5 and newer compile issues.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
-Added new recipe for IoTivity 0.9.2 framework, SDK and samples.
-Updated README for meta-oic.
-Modified iotivity-simple-client with an updated simpleclient example
and a Makefile to its source archive.
-Moved BBMASK directive for recipes-kernel (not everyone will want
to use it) to layer.conf.
-Removed old recipes for IoTivity 0.9.0 and 0.9.1, which are now
deprecated.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Updated IoTivity source patch-set to include i686
to list of supported architectures for the Yocto
platform.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
Signed-off-by: Juliet Cai <juliet.z.cai@intel.com>
|
|
* Updated recipe to download the released source files instead pulling from git repository
* Added a patch file to the Iotivity source code that
- adds libuuid back to the linked library list for yocto build in build_common/SConscript
- changes OICSensorboard application to work with updated APIs
Note: For OICSensorboard client to work properly, this patch must be applied on host machine
|
|
* Updated recipe to Point to the current tip of the 0.9.1-dev branch.
* Added hook to configure https_proxy to be used by the
IoTivity build process. This is applicable while performing
a build from behind a network proxy.
* Updated README with detais on the proxy setting.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
* Added new recipe iotivity_0.9.1.bb to fetch IoTivity
0.9.1 "pre-release" source code and perform build/packaging.
* Updated iotivity-simple-client sample to work with the new
release.
* Added linux-yocto 3.19 kernel configuration recipe (.bbappend)
to incorporate bluetooth and 6LoWPAN support in a resulting
OS image.
Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
|
|
-Moved location of 'inherit' directive so that Yocto
scons dependencies are picked up.
|
|
-Targets the Iotivity 0.9.0 release.
-Supports the resource layer of the Iotivity stack.
|