From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How-to export cross-toolchain and libraries to a build server?
Date: Tue, 11 Nov 2014 10:49:57 +0100 [thread overview]
Message-ID: <20141111104957.251e3809@free-electrons.com> (raw)
In-Reply-To: <156048fd0d6d4325bbe2ba0ff5b6e9e0@DB3PR04MB108.eurprd04.prod.outlook.com>
Dear Fabrice Mousset | GEOCEPT GmbH,
On Tue, 11 Nov 2014 09:43:02 +0000, Fabrice Mousset | GEOCEPT GmbH
wrote:
> thanks a lot for your quick reply.
> I will follow your advice and use BR2_HOST_DIR to fixe SDK location.
> So I will have a quick solution to move the SDK to our build server.
Ok. Let us know if that works.
> I will also take a closer look at the TODO list, and perhaps I could contribute to buildroot to help integrating a relocatable SDK generation, which will be a very nice and useful feature.
> But I think, I will have to learn a lot of thinks about the internals of buildroot before.
Sure, your contributions would be very welcome! But indeed, working on
making the SDK relocatable is clearly not the easiest thing to get
started with the Buildroot internals.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-11 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 7:28 [Buildroot] How-to export cross-toolchain and libraries to a build server? Fabrice Mousset | GEOCEPT GmbH
2014-11-11 9:25 ` Thomas Petazzoni
2014-11-11 9:43 ` Fabrice Mousset | GEOCEPT GmbH
2014-11-11 9:49 ` Thomas Petazzoni [this message]
2014-11-11 12:10 ` Fabrice Mousset | GEOCEPT GmbH
2014-11-11 13:00 ` Thomas Petazzoni
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=20141111104957.251e3809@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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