Skip to content

feat: permit use of system rapidyaml#1305

Merged
johnbartholomew merged 1 commit intogoogle:masterfrom
jcpunk:system-rapidyaml
Mar 9, 2026
Merged

feat: permit use of system rapidyaml#1305
johnbartholomew merged 1 commit intogoogle:masterfrom
jcpunk:system-rapidyaml

Conversation

@jcpunk
Copy link
Contributor

@jcpunk jcpunk commented Mar 9, 2026

This addresses the TODO to permit use of the system rapidyaml rather than the vendored files.

In theory this should make packaging a bit more consistent across various build environments.

I'd love to see this in 0.22.0

@johnbartholomew
Copy link
Collaborator

I think this probably won't work as-is on Debian, because the libryml-dev package doesn't contain any CMake package config (or even any pkg-config files!): https://packages.debian.org/sid/amd64/libryml-dev/filelist

Might just be a Debian packaging problem, I'm not certain.

Signed-off-by: Pat Riehecky <riehecky@fnal.gov>
@jcpunk jcpunk force-pushed the system-rapidyaml branch from 8951f32 to 654796e Compare March 9, 2026 15:10
@jcpunk
Copy link
Contributor Author

jcpunk commented Mar 9, 2026

I'll confess, I'm mostly working on Fedora/RHEL which provide:

/usr/lib64/cmake/ryml/rymlConfig.cmake
/usr/lib64/cmake/ryml/rymlConfigVersion.cmake
/usr/lib64/cmake/ryml/rymlTargets-release.cmake
/usr/lib64/cmake/ryml/rymlTargets.cmake

@johnbartholomew
Copy link
Collaborator

Ok. Let's assume Debian packaging will catch up eventually.

@johnbartholomew johnbartholomew merged commit 654796e into google:master Mar 9, 2026
16 checks passed
@jcpunk jcpunk deleted the system-rapidyaml branch March 9, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants