From: "Joshua Watt" <JPEWhacker@gmail.com>
To: Sinan Kaya <okaya@kernel.org>, yocto@lists.yoctoproject.org
Subject: Re: [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk
Date: Tue, 17 Aug 2021 09:44:56 -0500 [thread overview]
Message-ID: <299fcf00-d052-fd02-694c-d23a19b3a98d@gmail.com> (raw)
In-Reply-To: <23ff22c9-a250-fd2c-c199-8392d331596a@gmail.com>
These 3 recipes are in meta-oe, not OE-core which means that the
bbappends are going to cause a dangling appends error/warning. Please
add a dynamic BBFILES pattern[1] so that these are conditionally applied
only if meta-oe is present, something like:
BBFILES_DYNAMIC += "\
openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-layer/recipes-*/*/*.bb
\
openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-layer/recipes-*/*/*.bbappend
\
"
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-BBFILES_DYNAMIC
On 8/17/21 9:33 AM, Joshua Watt wrote:
>
> On 8/17/21 9:07 AM, Sinan Kaya wrote:
>> Dynamically linked protoc.exe is failing as follows:
>>
>> [libprotobuf ERROR google/protobuf/descriptor_database.cc:641]
>> File already exists in database: google/protobuf/descriptor.proto
>> [libprotobuf FATAL google/protobuf/descriptor.cc:1371] CHECK failed:
>> GeneratedDatabase()->Add(encoded_file_descriptor, size):
>>
>> Switch to static linkage per upstream recommendation.
>>
>> Signed-off-by: Sinan Kaya <okaya@kernel.org>
>> ---
>> recipes-devtools/protobuf/protobuf_%.bbappend | 1 +
>> 1 file changed, 1 insertion(+)
>> create mode 100644 recipes-devtools/protobuf/protobuf_%.bbappend
>>
>> diff --git a/recipes-devtools/protobuf/protobuf_%.bbappend
>> b/recipes-devtools/protobuf/protobuf_%.bbappend
>> new file mode 100644
>> index 0000000..b53b22d
>> --- /dev/null
>> +++ b/recipes-devtools/protobuf/protobuf_%.bbappend
>> @@ -0,0 +1 @@
>> +EXTRA_OECONF:append:sdkmingw32 = " --disable-shared"
>
> Apologies, this should use the :mingw32 override, since it's not
> *specific* to the SDK, but MinGW in general. Anyway, I fixed this up
> for you since I wasn't clear; this is in master-next and I'll get it
> tested shortly
>
>
next prev parent reply other threads:[~2021-08-17 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:07 [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk Sinan Kaya
2021-08-17 14:07 ` [meta-mingw] [PATCH v2 2/3] protobuf-c: static link " Sinan Kaya
2021-08-17 14:07 ` [meta-mingw] [PATCH v2 3/3] grpc: static link tools when generating SDK Sinan Kaya
2021-08-17 14:33 ` [meta-mingw] [PATCH v2 1/3] protobuf: static link tools when generating sdk Joshua Watt
2021-08-17 14:44 ` Joshua Watt [this message]
2021-08-17 14:54 ` Sinan Kaya
2021-08-17 15:08 ` Sinan Kaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=299fcf00-d052-fd02-694c-d23a19b3a98d@gmail.com \
--to=jpewhacker@gmail.com \
--cc=okaya@kernel.org \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.