From: Robert Bielik <Robert.Bielik@dirac.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: RE: Root filesystem
Date: Thu, 30 Nov 2017 08:27:00 -0000 [thread overview]
Message-ID: <834dd57d07fa419aab2bc4057cb196c8@hosted3-mb01.itm.host> (raw)
In-Reply-To: <20171130082046.ytf7jok7r26lqnlf@tarshish>
Thank you Baruch,
Doh! Now I remember I have been looking at buildroot before, I just didn't think of using it in this way 😊
Regards
/R
> -----Original Message-----
> From: Baruch Siach [mailto:baruch@tkos.co.il]
> Sent: den 30 november 2017 09:21
> To: Robert Bielik <Robert.Bielik@dirac.com>
> Cc: crossgcc@sourceware.org
> Subject: Re: Root filesystem
>
> Hi Robert,
>
> On Thu, Nov 30, 2017 at 08:13:38AM +0000, Robert Bielik wrote:
> > New to the tool! I'm planning to use this for setting up a complete build
> > toolchain for Raspberry Pi 3. This means building f.i.
> ALSA/GStreamer/LADSPA
> > etc. etc. and installing them in the proper rootfs which will be packaged
> > together with the toolchain.
> >
> > I suspect this is out of the scope of the ct-ng tool ? Maybe someone has
> > ideas or pointers on how to accomplish this ?
>
> You can try Buildroot: https://buildroot.org
>
> You can use ct-ng to generate a toolchain and use it in Buildroot as an
> external toolchain. Or you can have Buildroot generate the toolchain for you
> (so called internal toolchain).
>
> baruch
>
> --
> http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2017-11-30 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 8:13 Robert Bielik
2017-11-30 8:20 ` Baruch Siach
2017-11-30 8:27 ` Robert Bielik [this message]
2017-11-30 14:30 ` Josh Branning
2017-11-30 15:34 ` Bill Randle
2017-11-30 15:36 ` Robert Bielik
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=834dd57d07fa419aab2bc4057cb196c8@hosted3-mb01.itm.host \
--to=robert.bielik@dirac.com \
--cc=baruch@tkos.co.il \
--cc=crossgcc@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).