Skip to contentSkip to conversation

protobuf: disable protoc binary for target

PATCH Superseded Vyacheslav Yurkov 2 participants 3 messages Aug 27, 2022

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 protobuf: disable protoc binary for target

From: Vyacheslav Yurkov <[email protected]>

When applications want to use protoc during the build, the target binary has to be disabled in order to avoid following error:

|   The imported target "protobuf::protoc" references the file
|
|      "<application build dir>/recipe-sysroot/usr/bin/protoc-<protobuf version>"
|
|   but this file does not exist.  Possible reasons include:
|
|   * The file was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and contained
|
|      "<application build dir>/recipe-sysroot/usr/lib/cmake/protobuf/protobuf-targets.cmake"
|
|   but not all the files it references.
---
 meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb | 7 +++++++
 1 file changed, 7 insertions(+)
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +7 -0
index 83dabc9f8..e36179363 100644
@@ -34,6 +34,13 @@ EXTRA_OECMAKE += "\
     -Dprotobuf_BUILD_EXAMPLES=OFF \
 "
 
+# Configuration below allows to cross-compile protobuf applications
+# and use native protoc binary in your recipes. In order to use protoc
+# on the target, set protobuf_BUILD_PROTOC_BINARIES to ON in your bbappend
+EXTRA_OECMAKE:append:class-target = " \
+     -Dprotobuf_BUILD_PROTOC_BINARIES=OFF \
+"
+
 TEST_SRC_DIR = "examples"
 LANG_SUPPORT = "cpp ${@bb.utils.contains('PACKAGECONFIG', 'python', 'python', '', d)}"
 
Signature · 1 line
2.25.1
#1 lore raw
Quoted 32 lines · Vyacheslav Yurkov

From: Vyacheslav Yurkov <[email protected]>

When applications want to use protoc during the build, the target binary has to be disabled in order to avoid following error:

|   The imported target "protobuf::protoc" references the file
|
|      "<application build dir>/recipe-sysroot/usr/bin/protoc-<protobuf version>"
|
|   but this file does not exist.  Possible reasons include:
|
|   * The file was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and contained
|
|      "<application build dir>/recipe-sysroot/usr/lib/cmake/protobuf/protobuf-targets.cmake"
|
|   but not all the files it references.
---
 meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb | 7 +++++++
 1 file changed, 7 insertions(+)
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +0 -0
index 83dabc9f8..e36179363 100644

meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb EXTRA_OECMAKE += "\ · line 43

Quoted 10 lines
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +7 -0
@@ -34,6 +34,13 @@ EXTRA_OECMAKE += "\
     -Dprotobuf_BUILD_EXAMPLES=OFF \
 "
 
+# Configuration below allows to cross-compile protobuf applications
+# and use native protoc binary in your recipes. In order to use protoc
+# on the target, set protobuf_BUILD_PROTOC_BINARIES to ON in your bbappend
+EXTRA_OECMAKE:append:class-target = " \
+     -Dprotobuf_BUILD_PROTOC_BINARIES=OFF \
+"
+

can we make it a packageconfig perhaps ?

Quoted 15 lines
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +0 -1
 TEST_SRC_DIR = "examples"
 LANG_SUPPORT = "cpp ${@bb.utils.contains('PACKAGECONFIG', 'python', 'python', '', d)}"
 
--

2.25.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#98486): https://lists.openembedded.org/g/openembedded-devel/message/98486
Mute This Topic: https://lists.openembedded.org/mt/93286129/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#2 lore raw
Quoted 35 lines · Khem Raj
Quoted 34 lines · Vyacheslav Yurkov

From: Vyacheslav Yurkov <[email protected]>

When applications want to use protoc during the build, the target binary has to be disabled in order to avoid following error:

|   The imported target "protobuf::protoc" references the file
|
|      "<application build dir>/recipe-sysroot/usr/bin/protoc-<protobuf version>"
|
|   but this file does not exist.  Possible reasons include:
|
|   * The file was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and contained
|
|      "<application build dir>/recipe-sysroot/usr/lib/cmake/protobuf/protobuf-targets.cmake"
|
|   but not all the files it references.
---
  meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb | 7 +++++++
  1 file changed, 7 insertions(+)
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +0 -0
index 83dabc9f8..e36179363 100644
@@ -34,6 +34,13 @@ EXTRA_OECMAKE += "\
      -Dprotobuf_BUILD_EXAMPLES=OFF \
  "
 
Quoted 9 lines

meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb EXTRA_OECMAKE += "\ · line 43

Quoted 7 lines
meta-oe/recipes-devtools/protobuf/protobuf_3.21.5.bb +7 -0
+# Configuration below allows to cross-compile protobuf applications
+# and use native protoc binary in your recipes. In order to use protoc
+# on the target, set protobuf_BUILD_PROTOC_BINARIES to ON in your bbappend
+EXTRA_OECMAKE:append:class-target = " \
+     -Dprotobuf_BUILD_PROTOC_BINARIES=OFF \
+"
+

can we make it a packageconfig perhaps ?

Makes sense. Any suggestions about the name? So far only something like "compiler" comes to mind.

Vyacheslav