From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcrossguid: bump to version 0.2.2
Date: Sun, 29 Apr 2018 11:27:18 +0200 [thread overview]
Message-ID: <mofgrexjul.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180428200043.2509-1-fontaine.fabrice@gmail.com
Am Sat, 28 Apr 2018 22:00:43 +0200 schrieb Fabrice Fontaine:
> -LIBCROSSGUID_VERSION = 8f399e8bd4252be9952f3dfa8199924cc8487ca4
> +LIBCROSSGUID_VERSION = v0.2.2
Hi,
building the only package depending on libcrossguid, Kodi, breaks due to
this bump:
/home/buildroot/br4/output/build/kodi-17.6-Krypton/xbmc/utils/
StringUtils.cpp: In static member function ?static std::__cxx11::string
StringUtils::CreateUUID()?:
/home/buildroot/br4/output/build/kodi-17.6-Krypton/xbmc/utils/
StringUtils.cpp:1194:10: error: ?GuidGenerator? does not name a type
static GuidGenerator guidGenerator;
^~~~~~~~~~~~~
/home/buildroot/br4/output/build/kodi-17.6-Krypton/xbmc/utils/
StringUtils.cpp:1195:15: error: ?guidGenerator? was not declared in this
scope
auto guid = guidGenerator.newGuid();
^~~~~~~~~~~~~
This happens due to changes in libcrossguid:
https://github.com/graeme-hill/crossguid/blob/master/README.md
"This is version 0.2 of CrossGuid. If you all already using CrossGuid and
your code uses GuidGenerator then you are using version 0.1."
Even Kodi master branch has no support for libcrossguid-0.2.x yet so I
vote for reverting this bump.
Regards, bernd
prev parent reply other threads:[~2018-04-29 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 20:00 [Buildroot] [PATCH 1/1] libcrossguid: bump to version 0.2.2 Fabrice Fontaine
2018-04-28 20:08 ` Thomas Petazzoni
2018-04-29 9:27 ` Bernd Kuhls [this message]
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=mofgrexjul.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox