[FR] Linux - Yocto support

### Feature proposal

* Firebase Component: All

Describe your use case and/or feature request here.

Enable cross compiling using Yocto/open-embedded. This enables building for any machine/architecture from an x86_64 host.

Building a Yocto image is a custom Linux distro and the defacto standard for commercial products on Linux.

A Yocto build has two build passes:
1. native (tools that run on host side)
2. target (binaries that run on the device)

There are no cases where you build both in the same pass.

Yocto will cache all source in a "fetch" stage. This enable LTS scenarios. Meaning no network access during configuration and compile. This enables rebuilding from source at a much later time without network access.

Something else Yocto enables is reproducible builds. Meaning you build today or ten years, and the bits will be identical.

Yocto has multiple branches. Some have LTS support. For a given branch it sticks with a particular set of versions. Kirkstone for example is on clang-14. Dunfell is on clang-12.

The standard approach in scenarios with complex CMake integrations is to use the system libraries, as these are controlled in Yocto. Then one patches core source as needed based on the Yocto branch.

One example of a Yocto recipe that deals with a complex CMake project is Google Filament:
https://github.com/jwinarske/meta-vulkan/blob/kirkstone/recipes-graphics/filament/filament-vk_1.4.92.bb

The base recipe is dependent on the -native variant. So the host tools are built in the -native build pass, then are used in the target build pass.

My feature request / proposal is to enable support for Yocto while maintaining existing build behavior. I am willing to do the work (submit the PRs) if there is willingness to collaborate.

Aucun fichier du dépôt ni aucun test n’est nommé. Commencez par examiner le comportement de build CMake existant et la recette Yocto de Google Filament liée, puis déterminez comment les passes de build native et target correspondraient à ce SDK. Le travail sera considéré comme terminé lorsque la prise en charge de Yocto sera définie et implémentée sans casser les builds existants.

Rédigé par le modèle d'indexation à partir du texte de l'issue.