llvm dev - Nov 2019 - Using the Yocto Project for Upstream Testing

Greetings All,

I've already mentioned this on the GCC side but it seems that the Yocto 
Project

has a class for testing upstream projects. The project is used for 
building embedded

distributions but due to the ability with bitbake and the amount of 
supported upstream

projects I've asked them to mention that other projects are interested 
in seeing this

happen at the usual Embedded Linux/IOT conference meeting they have yearly.

Just getting the LLVM side note that its already been discussed with them,

Nick

Sorry, I'm not sure I follow/understand your email, or what sort of
replies/responses/discussion you're hoping to get from it - perhaps you
could rephrase and/or provide more detail?

On Sat, Nov 16, 2019 at 3:59 PM Nicholas Krause via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Greetings All,
>
> I've already mentioned this on the GCC side but it seems that the Yocto
> Project
>
> has a class for testing upstream projects. The project is used for
> building embedded
>
> distributions but due to the ability with bitbake and the amount of
> supported upstream
>
> projects I've asked them to mention that other projects are interested
> in seeing this
>
> happen at the usual Embedded Linux/IOT conference meeting they have yearly.
>
> Just getting the LLVM side note that its already been discussed with them,
>
> Nick
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191122/d2b05d9d/attachment.html>

On 11/22/19 2:46 PM, David Blaikie wrote:
> Sorry, I'm not sure I follow/understand your email, or what sort of 
> replies/responses/discussion you're hoping to get from it - perhaps 
> you could rephrase and/or provide more detail?
David,

Sorry its more to give you guys a heads up in case they ask about it 
being of interest and know that
its something of interest outside that project.  The Yocto and its 
related projects are a embedded build
system. Since its goal is to build the whole custom embedded 
distribution I've suggested that they start
testing upstream gcc/llvm.

My reasoning is that while we have a testsuite for both having a 
software that builds and supports lots
of real software can be of use. To my knowledge it has the ability to 
build over 10000 open source
packages.

Basically the idea is to automate testing of not just the testsuite but 
a suite of real software builds
nightly or so as it takes time to build all that software. You can of 
course just build one piece of
software and its dependencies separate through.

This is a link to the project:https://www.yoctoproject.org/
And a link to all the recipes for building software it supports that are 
upstreamed:
https://layers.openembedded.org/layerindex/branch/master/recipes/

The GCC side knows as well but thought I would give you guys the heads 
up as well and sorry for not
explaining it better,
Nick
>
> On Sat, Nov 16, 2019 at 3:59 PM Nicholas Krause via llvm-dev 
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at
lists.llvm.org>> wrote:
>
>     Greetings All,
>
>     I've already mentioned this on the GCC side but it seems that the
>     Yocto
>     Project
>
>     has a class for testing upstream projects. The project is used for
>     building embedded
>
>     distributions but due to the ability with bitbake and the amount of
>     supported upstream
>
>     projects I've asked them to mention that other projects are
>     interested
>     in seeing this
>
>     happen at the usual Embedded Linux/IOT conference meeting they
>     have yearly.
>
>     Just getting the LLVM side note that its already been discussed
>     with them,
>
>     Nick
>
>     _______________________________________________
>     LLVM Developers mailing list
>     llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>     https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20191122/7d2e89b6/attachment.html>