On Wed, May 1, 2019 at 9:04 AM Matthew Stanger <matthew_stan...@trimble.com> wrote: > > `protoc` sourced by the standard Yocto SDK will fail to import "well > known" supporting protobufs. > > Steps to reproduce: > > 1. Generated SDK with `protoc` via `DEPENDS = "protobuf-native"` > 2. Source SDK & run `protoc *.proto --cpp_out=.`
This is not a problem with the protobuf recipe, but in how the SDK was configured. I just need to make the following changes to our image's bbappend file and all of the protobuf headers were properly added to the SDK we are generating $ git diff diff --git a/recipes-core/images/core-image-renew.bbappend b/recipes-core/images/core-image-renew.bbappend index 5d75531..198526f 100644 --- a/recipes-core/images/core-image-renew.bbappend +++ b/recipes-core/images/core-image-renew.bbappend @@ -1 +1,2 @@ -TOOLCHAIN_HOST_TASK += "nativesdk-protobuf-compiler" +TOOLCHAIN_HOST_TASK += "nativesdk-protobuf-dev" +TOOLCHAIN_TARGET_TASK += "protobuf-dev" Once I built the SDK with that change in place, the project using protobuf during build had no problem building using the SDK. Ted Roth -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
