[CFP] Switching to LLVM based toolchains in Yocto based distributions
berolinux opened this issue · 1 comments
Title
Switching to LLVM based toolchains in Yocto based distributions
Author
Bernhard Rosenkraenzer, bero@lindev.ch, Huawei Open Source Technology Center
Distribution
Yet unnamed embedded distribution (current working title: All Scenarios OS)
Abstract (optional)
The Huawei Open Source Technology Center is working on a new distribution for embedded devices, using the Linux kernel for higher end devices and the Zephyr kernel for the low end.
Like many embedded distributions, it is based on Yocto - but unlike most others, it uses LLVM/Clang as its primary toolchain.
The talk shows how it can be done, and goes over some issues currently in the way.
What's unique about the environment you package LLVM for? (optional)
Multi-kernel, multi-architecture embedded distribution using clang as its primary compiler
What makes your distribution of LLVM unique? (optional)
Crosscompiling with a Yocto based build system
What might others learn from your experience? (optional)
How to use clang in a Yocto/OpenEmbedded environment
What could be improved in upstream LLVM to make working with it easier as a downstream packager? (optional)
More help for not so experienced packagers who report "MyFavoriteApp 1.1 works great with gcc but crashes with clang. Obviously clang is to blame and needs to be fixed, let's switch back to gcc!" type "bugs" -- There's currently no really good place for newbie packages to turn to for help.
Thanks for taking the time to write up a CFP; we'd be overjoyed to have you present at LLVM Distributors Conf 2021! If you still plan on presenting, this is a reminder to get started on your slides for next week. Once they're done, we will contact you about submitting a PDF of your slides as either a pull request to this repository or via email to the organizer. We hope to have a schedule finalized by EOW; we may iterate on the schedule based on whether presenters have conflicts. Please keep this issue open for attendees to ask questions, or close this issue if you no longer plan on attending. Reminder to keep your talk concise (15 minutes); we wont be doing time for questions in order to fit as much content as possible. Attendees should ask questions here in this github issue.