Hi Anatol, Stefan, On Wed, 3 Mar 2021 at 16:27, Anatol Belski <[email protected]> wrote: > > Hi, > > On 3/2/2021 8:13 PM, Clément Péron wrote: > > Hi Stefan, > > Le mar. 2 mars 2021 à 19:38, Stefan Herbrechtsmeier > <[email protected]> a écrit : >> >> Hi, >> >> Am 02.03.21 um 19:22 schrieb Anatol Belski: >> > >> > On 3/2/2021 5:06 PM, Clément Péron wrote: >> >>> I don't use this feature from the grpc package, only linking against the >> >>> libs. However I don't see why this should be an issue, as all the >> >>> *.cmake files are packaged. I see that in the RPMs but also in a recipe >> >>> of a dependent packgae like this >> >> Yes the cmake file is found but not the grpc_cpp_plugin. >> >> >> >> This is due to cmake looking for the grpc_cpp_plugin in the target >> >> sysroot instead of the native/host sysroot. >> >> >> >>> $ ls -l ./tmp/work/*/*/*/recipe-sysroot/usr/lib/cmake/grpc/*.cmake >> >>> >> >>> Or use recipe-sysroot-native depending on the consuming recipe. >> >>> >> >>> Just a wild guess here - does your recipe put 'grpc' into DEPENDS or >> >>> RDEPENDS, etc. >> >> In my recipe I put 'grpc' and 'grpc-native' into DEPENDS using >> >> PACKAGECONFIG >> >> PACKAGECONFIG[grpc] = "-DCONFIG_GRPC=ON,-DCONFIG_GRPC=OFF,grpc >> >> grpc-native" >> >> >> >>> Also, do you inherit cmake in your recipe? >> >> Yes i am indeed inheriting cmake and also systemd in my recipe >> >> >> >>> It seems to me >> >>> that it's more about how to use cmake files in a recipe, as the >> >>> particularly mentioned files are packaged and pulled in a consuming >> >>> recipe. >> >> When I look in the files packaged the cmake file is indeed here. >> >> The issue is coming from the gRPCTargets.cmake >> >> (https://pastebin.com/bZay7cew) >> >> Line 159: >> >> # Create imported target gRPC::grpc_cpp_plugin >> >> add_executable(gRPC::grpc_cpp_plugin IMPORTED) >> >> >> >> [snip] >> >> > The executables seem only be useful for dev and thus only as native. At >> > this point it seems it's about going deep into debugging your recipe, as >> > seems there's no solution laying on the surface. >> >> This is a knowing issue and I have try to fix grpc but yocto is not a >> platform grpc officially support: >> https://github.com/grpc/grpc/pull/22498 > > > thanks for chiming in, Stefan. So this is a known issue and upstream has > refused the patch. > > his patch makes sense to me > > Can't we include it in meta-oe ? > > I will apply it locally anyway. > > Clément, is it so far confirmed that your issue is fixed by teh patch?
Yes it is, Building my recipe just by adding the CMake patch. Just a question: is it normal that grpc_cpp_plugin host is not installed in the nativesdk automatically? Maybe we should separate in the recipe the gRPC compiler/plugins and gRPC libs no ? Like it's done by protobuf: http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-devtools/protobuf/protobuf_3.15.2.bb#n74 Regards, Clement > > I could note from my side, that carrying a patch to CMake scripts in general > is a pain, as the syntax is not very patch friendly. For GRPC - the CMake > script is also huge. But also, i've no use for the pattern so couldn't tell > how urgent this scenario would be. > > > Thanks > > Anatol > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#89879): https://lists.openembedded.org/g/openembedded-devel/message/89879 Mute This Topic: https://lists.openembedded.org/mt/80753655/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
