Pulling down things from the network in do_install() is not the best option. Is reproducibility and integrity of such downloads guaranteed? What about the component licensing, where is that checked (against upstream changes)? Also, yocto's download caching and mirroring facility is side-stepped entirely.
The typical 'Yocto way' would be to write a specific conan fetcher for bitbake, so that you can specify SRC_URI = "conan://..." in recipes: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/bb/fetch2?h=master-next Generally, if someone is doing system integration with Yocto and has access to the source code, they might just write actual component recipes for building from source, as the presented workflow with building via SDK and artifactory binary uploads is awkward, and all benefits that happen when yocto is able to build directly from source code are lost. Regards, Alex On Fri, 26 Jul 2019 at 14:39, Dani Manzaneque <danimanzane...@gmail.com> wrote: > Hi! > > We have developed an integration with Yocto for the open-source Conan > C/C++ package manager. > This integration includes the ability to cross-build packages with a > Yocto SDK Toolchain and later deploy them in the Yocto build. > > We have created a blog post with a brief introduction to the Yocto > Project and the announcement of the integration: > https://blog.conan.io/2019/07/26/Conan-Yocto-integration.html > > And a detailed section in our documentation with the configuration for > the meta-conan layer and the Bitbake recipes for the packages: > https://docs.conan.io/en/latest/integrations/cross_platform/yocto.html > > Feedback is welcomed. Thanks a lot! > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto