utfcpp: add recipe
The documentation states:
This is a header-only library and the supported way of deploying it is:
Download a release from <https://github.com/nemtrif/utfcpp/releases> into a temporary directory Unzip the release Copy the content of utfcpp/source file into the directory where you keep include files for your project
The CMakeList.txt file was originally made for testing purposes only, but unfortunately over time I accepted contributions that added install target. /This is not a supported way of installing the utfcpp library/ and I am considering removing the CMakeList.txt in a future release.
This statement doesn't make a lot of sense to me but maybe it would be a good idea to install the files manually instead of using cmake?
Quoted 62 lines · Markus Volk
utfcpp will be a required dependency for the upcoming taglib-2.0 update.
Signed-off-by Markus Volk <[email protected] <mailto:[email protected]>>--- meta/conf/distro/include/maintainers.inc | 1 + meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb | 13 +++++++++++++ 2 files changed, 14 insertions(+) create mode 100644 meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bbmeta/conf/distro/include/maintainers.inc +0
-0@@ -824,6 +824,7 @@ RECIPE_MAINTAINER:pn-unzip = "Denys Dmytriyenko<[email protected]>"
RECIPE_MAINTAINER:pn-update-rc.d = "Ross Burton <[email protected]
<mailto:[email protected]>>"
RECIPE_MAINTAINER:pn-usbinit = "Alexander Kanavin
<[email protected] <mailto:[email protected]>>"
RECIPE_MAINTAINER:pn-usbutils = "Alexander Kanavin
<[email protected] <mailto:[email protected]>>" +RECIPE_MAINTAINER:pn-utfcpp = "Markus Volk <[email protected] <mailto:[email protected]>>"
RECIPE_MAINTAINER:pn-util-linux = "Chen Qi <[email protected]
<mailto:[email protected]>>"
RECIPE_MAINTAINER:pn-util-linux-libuuid = "Chen Qi
<[email protected] <mailto:[email protected]>>"
RECIPE_MAINTAINER:pn-util-macros = "Unassigned
<[email protected] <mailto:[email protected]>>"meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb new file +4
-0@@ -0,0 +1,13 @@ +SUMMARY = "UTF-8 with C++ in a Portable Way." +HOMEPAGE = "<https://github.com/nemtrif/utfcpp>" +LICENSE = "BSL-1.0" +LIC_FILES_CHKSUM ="file://LICENSE;md5=e4224ccaecb14d942c71d31bef20d78c" <file://license;md5=e4224ccaecb14d942c71d31bef20d78c/>
meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb new file +2
-0+ +SRC_URI ="
git://github.com/nemtrif/utfcpp.git;protocol=https;branch=master"meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb new file +7
-1+ +SRCREV = "aed58281cf45838bdb7296e3109bd5a633d677ed" +S = "${WORKDIR}/git" + +inherit cmake + +FILES:${PN}-dev += "${datadir}/utf8cpp/cmake" --2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193230): <https://lists.openembedded.org/g/openembedded-core/message/193230>
Mute This Topic: <https://lists.openembedded.org/mt/103480458/3618223>
Group Owner: [email protected] <mailto:[email protected]>
Unsubscribe: <https://lists.openembedded.org/g/openembedded-core/unsub> [[email protected] <mailto:[email protected]>]
-=-=-=-=-=-=-=-=-=-=-=-
I wonder if we even need a separate recipe at all. Perhaps just list this in SRC_URI for taglib and copy the needed file out of its tree into where taglib can pick it up?
Alex
Quoted 29 lines · Markus Volk
The documentation states:
This is a header-only library and the supported way of deploying it is:
Download a release from https://github.com/nemtrif/utfcpp/releases into a temporary directory Unzip the release
Copy the content of utfcpp/source file into the directory where you keep include files for your projectThe CMakeList.txt file was originally made for testing purposes only, but unfortunately over time I accepted contributions that added install target. This is not a supported way of installing the utfcpp library and I am considering removing the CMakeList.txt in a future release.
This statement doesn't make a lot of sense to me but maybe it would be a good idea to install the files manually instead of using cmake?
On Tue, Jan 2 2024 at 01:52:14 PM +01:00:00, Markus Volk <[email protected]> wrote:
utfcpp will be a required dependency for the upcoming taglib-2.0 update. Signed-off-by: Markus Volk <[email protected]> --- meta/conf/distro/include/maintainers.inc | 1 + meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb | 13 +++++++++++++ 2 files changed, 14 insertions(+) create mode 100644 meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb diff --git a/meta/conf/distro/include/maintainers.inc b/meta/conf/distro/include/maintainers.inc index
8dc63b138e..f0a39beffd100644 --- a/meta/conf/distro/include/maintainers.inc +++ b/meta/conf/distro/include/maintainers.inc @@ -824,6 +824,7 @@ RECIPE_MAINTAINER:pn-unzip = "Denys Dmytriyenko <[email protected]>" RECIPE_MAINTAINER:pn-update-rc.d = "Ross Burton <[email protected]>" RECIPE_MAINTAINER:pn-usbinit = "Alexander Kanavin <[email protected]>" RECIPE_MAINTAINER:pn-usbutils = "Alexander Kanavin <[email protected]>" +RECIPE_MAINTAINER:pn-utfcpp = "Markus Volk <[email protected]>" RECIPE_MAINTAINER:pn-util-linux = "Chen Qi <[email protected]>" RECIPE_MAINTAINER:pn-util-linux-libuuid = "Chen Qi <[email protected]>" RECIPE_MAINTAINER:pn-util-macros = "Unassigned <[email protected]>" diff --git a/meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb b/meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb new file mode 100644 index 0000000000..9cbea94c63 ---/dev/null+++ b/meta/recipes-devtools/utfcpp/utfcpp_4.0.4.bb @@ -0,0 +1,13 @@ +SUMMARY = "UTF-8 with C++ in a Portable Way." +HOMEPAGE = "https://github.com/nemtrif/utfcpp" +LICENSE = "BSL-1.0" +LIC_FILES_CHKSUM = "file://LICENSE;md5=e4224ccaecb14d942c71d31bef20d78c" + +SRC_URI = "git://github.com/nemtrif/utfcpp.git;protocol=https;branch=master" + +SRCREV = "aed58281cf45838bdb7296e3109bd5a633d677ed" +S = "${WORKDIR}/git" + +inherit cmake + +FILES:${PN}-dev += "${datadir}/utf8cpp/cmake" --
2.43.0-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193232): https://lists.openembedded.org/g/openembedded-core/message/193232
Mute This Topic: https://lists.openembedded.org/mt/103480458/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Quoted 3 lines · Alexander Kanavin
I wonder if we even need a separate recipe at all. Perhaps just list this in
SRC_URIfor taglib and copy the needed file out of its tree into where taglib can pick it up?
<https://github.com/taglib/taglib/blob/ef013b76dbfa8a5d8e5027d6c285bc9699f71208/CMakeLists.txt#L153>
taglib currently only supports cmake for finding utfcpp. It would be possible to use gitsm fetcher to get the utfcpp code, if the recipe gets converted to git but also for that case it will utilize 3rdparty/utfcpp/CMakeLists.txt to install it.
So do I understand correctly that the two upstreams mutually contradict each other? Can you file a ticket with one or the other?
Alex
Quoted 9 lines · On Tue, 2 Jan 2024 at 18:37, <[email protected]> wrote:
On Tue, Jan 2 2024 at 05:43:31 PM +01:00:00, Alexander Kanavin <[email protected]> wrote:
I wonder if we even need a separate recipe at all. Perhaps just list this in
SRC_URIfor taglib and copy the needed file out of its tree into where taglib can pick it up?https://github.com/taglib/taglib/blob/ef013b76dbfa8a5d8e5027d6c285bc9699f71208/CMakeLists.txt#L153
taglib currently only supports cmake for finding utfcpp. It would be possible to use gitsm fetcher to get the utfcpp code, if the recipe gets converted to git but also for that case it will utilize
3rdparty/utfcpp/CMakeLists.txtto install it.
Quoted 2 lines · Alexander Kanavin
So do I understand correctly that the two upstreams mutually contradict each other?
<https://github.com/nemtrif/utfcpp/commit/4965d378fb141a21c8afa7c283a8af4725e6a57e>
The announcement to deprecate support for cmake in utfcpp was made only recently.
At the moment, cmake is still supported and in my opinion should not be declared obsolete. Maintaining CMakeLists.txt for a header-only library doesn't seem like that much work. This smells like an ideological discussion to me.
Lets wait and see how the taglib developers will react. Until then, it seems to make sense to use cmake because it is nicely integrated into taglib