From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Questions regarding adding a new llvm based cross-compiler
Date: Fri, 17 Oct 2014 19:48:24 +0200 [thread overview]
Message-ID: <20141017174824.GR3000@jama> (raw)
In-Reply-To: <CANyK_8cvEcxAC3tJMJHSif01gnXZU=L=TTu990_uENTrjTYK1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Fri, Oct 17, 2014 at 09:07:19AM +0100, Paul Barker wrote:
> On 16 October 2014 18:46, Cody P Schafer <dev@codyps.com> wrote:
> > Hi all,
> >
> > I'm working on creating a layer for the rust compiler (which uses
> > llvm) and was wondering if there were any best practices and/or
> > examples people could point me at.
Are you using llvm recipes from meta-oe (or at least starting from
them)?
> I can't really offer much help on the LLVM side, but I can say this
> will be really useful work. I'm slowly learning Rust and researching
> how it can be used for embedded development and it will be excellent
> to have a rust compiler working as part of OpenEmbedded/Yocto.
>
> If you need any testing of this layer once it's created, just let me know.
I'm also interested.
I haven't tried it yet, but I've asked Servo developer, how they do
cross-builds and he said that it's really simple with Rust and Cargo,
which support cross-compilation by design.
Now reading:
http://doc.crates.io/faq.html#does-cargo-handle-multi-platform-projects-or-cross-compilation?
it doesn't looks so convincing, but I would be happy to test.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-10-17 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 17:46 Questions regarding adding a new llvm based cross-compiler Cody P Schafer
2014-10-17 8:07 ` Paul Barker
2014-10-17 17:48 ` Martin Jansa [this message]
2014-10-20 19:45 ` Cody P Schafer
2014-10-19 8:10 ` Khem Raj
2014-10-20 19:47 ` Cody P Schafer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141017174824.GR3000@jama \
--to=martin.jansa@gmail.com \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.