From: Joey Oravec <joravec@drewtech.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openembedded with a prebuilt external toolchain
Date: Thu, 10 Feb 2011 18:22:51 -0500 [thread overview]
Message-ID: <4D54734B.7060705@drewtech.com> (raw)
In-Reply-To: <4D545173.8080904@mentor.com>
On 2/10/2011 3:58 PM, Tom Rini wrote:
> We talked about this a little on IRC and I provided the example of how
> to use the CodeSourcery recipes that exist today. The marvell
> toolchain however will need it's own special love.
Yes! Much appreciated!
> Now what you'll want to do is make an external-toolchain-marvell.bb
> and set TOOLCHAIN_BRAND to "marvell" and tweak TOOLCHAIN_VENDOR such
> that we go from what OE normally says TARGET_SYS is to what your tools
> actually say it is. Then it's a matter of tweaking the contents of
> external-toolchain-marvell.bb to copy the right things out of the
> marvell install and into where OE wants them. In this regard, the
> -csl recipe may be more instructive than the -generic recipe as the
> -generic recipe (along with external-toolchain.bb) are targeted at
> toolchains exported by OE and thus require little mangling to work.
Both the -csl.bb and -generic.bb copy a bunch of stuff to STAGING_DIR in
do_stage(). Of course in the long-run I need for the recipe to copy C
libraries, but for now I should be able to leave the body blank. At
least it'll use my compiler and run to completion. Right?
That's what I did and it seems to be ok. The "bitbake nano" example
failed, looks like it wasn't linking ncurses. Another attempt with
"bitbake busybox" worked and I saw some packages in the output folder.
Looks good so far!
-joey
next prev parent reply other threads:[~2011-02-10 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 20:24 openembedded with a prebuilt external toolchain Joey Oravec
2011-02-10 20:58 ` Tom Rini
2011-02-10 23:22 ` Joey Oravec [this message]
2011-02-10 23:35 ` Tom Rini
2011-02-14 20:14 ` Joey Oravec
2011-03-02 16:02 ` Denys Dmytriyenko
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=4D54734B.7060705@drewtech.com \
--to=joravec@drewtech.com \
--cc=openembedded-devel@lists.openembedded.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.