mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-08-28 23:30:21 +00:00
Khem Raj
bdc9913b3f
restinio 0.7.x is a major architectural change from 0.6.x: the release tarball no longer bundles any of its third-party dependencies (http_parser, expected-lite, fmt, catch2, sobjectizer). They must now be supplied externally and resolved through find_package()/system linkage. This requires two new supporting recipes added in prior commits: llhttp (replacement for the now-dropped http_parser) and expected-lite (nonstd::expected backport, now required unconditionally instead of restinio's old embedded fallback). asio, fmt and catch2 dependencies are already satisfied by existing recipes in the tree. Recipe changes: - Release tag format changed from "v.X.Y.Z" to "vX.Y.Z"; update SRC_URI and SRC_URI[sha256sum] accordingly. - LIC_FILES_CHKSUM md5 updated for the new tarball's root LICENSE file. - DEPENDS: drop http-parser, add llhttp and expected-lite. - EXTRA_OECMAKE: RESTINIO_FIND_DEPS and RESTINIO_USE_EXTERNAL_HTTP_PARSER were removed upstream. RESTINIO_BENCH renamed to RESTINIO_BENCHMARK, RESTINIO_ALLOW_SOBJECTIZER renamed to RESTINIO_WITH_SOBJECTIZER (kept disabled). Added RESTINIO_DEP_STANDALONE_ASIO=find, RESTINIO_DEP_FMT=find and RESTINIO_DEP_EXPECTED_LITE=find so restinio's CMakeLists.txt resolves these via find_package() instead of trying to add_subdirectory() vendored sources that no longer exist in the tarball. RESTINIO_DEP_LLHTTP=system is used instead of "find" because llhttp's own CMakeLists.txt only exports an "llhttp::llhttp_shared" imported target (llhttp::llhttp is just a build-tree ALIAS, never installed/exported), which restinio's dependency-resolution logic does not recognize as a valid find_package() target name. AI-Generated: Uses Claude Code Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Collection of layers for the OE-core universe
Main layer maintainer: Khem Raj raj.khem@gmail.com
This repository is a collection of layers to supplement OE-Core with additional packages, Each layer have designated maintainer Please see the respective READMEs in the layer subdirectories