meta-oqs Yocto layer update with demos and language bindings

[embetrix]

Hi OQS team,

I’ve reworked my Yocto/OpenEmbedded integration layer meta-oqs to track the latest liboqs and oqs-provider releases:

https://github.com/embetrix/meta-oqs

The layer now includes working demo setups (classical, hybrid, and pure PQC) for:

• NGINX

• OpenVPN

• SSH

• MQTT

The integration of oqs-provider with OpenSSL is seamless within the Yocto build, enabling oqs-provider by default and hybrid and PQC TLS groups without manual configuration.

I also added Python, C++ and Rust bindings to make experimentation with liboqs easier on embedded targets.

The layer has been built and tested on multiple targets (ARM, ARM64 and x86_64) and is working as expected.

Feedback is very welcome.

[baentsch]

Thanks for making us aware of this @embetrix : Nice work! I wonder whether this should be highlighted (added?) at https://github.com/open-quantum-safe/oqs-demos and/or maybe even replace some of the integrations there (if only to reduce duplicate efforts)?

[embetrix]

@baentsch Thanks, I would definitely appreciate being referenced from oqs-demos or anywhere within the open-quantum-safe GitHub organization.

The scope of meta-oqs is somehow different from oqs-demos. While oqs-demos focuses on container-based showcase integrations, meta-oqs aims at reproducible integration of liboqs and oqs-provider within Yocto/OpenEmbedded aligned with Yocto release cycles and tightly integrated with distribution package versions. It targets embedded Linux systems running on real hardware (ARM/ARM64/x86_64).

I see it more as complementary integration layer for embedded evaluation rather than a direct replacement of the existing demos.

I’m happy to align structure or documentation if that helps reduce overlap and improve consistency.