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 14:00:57 +0100 [thread overview]
Message-ID: <20141111140057.24538411@free-electrons.com> (raw)
In-Reply-To: <20833d047f3d4434b8eb867b1a46b526@DB3PR04MB108.eurprd04.prod.outlook.com>
Hello,
On Tue, 11 Nov 2014 12:10:22 +0000, Fabrice Mousset | GEOCEPT GmbH
wrote:
> it works :-)
Cool!
> I have built my BSP with BR2_HOST_DIR (make BR2_HOST_DIR=/opt/crosstools/am335x) and made an archive of it (tar cJf am335x-sdk.tar.xz /opt/crosstools/am335x). Then expand this archive on the build server.
> And it simply works, Jenkins is now able to build Qt5 projects for my board.
Great.
> The SDK is quiet big (about 57MB), but it is a simple and quick solution.
57 MB are you sure? This looks very small to me, when you count the
toolchain + all the Qt5 libraries and headers.
> I will try to spend time on "relocatable SDK generation" in the next weeks to see if an easier/smarter solution is possible.
Great, looking forward to see contributions in this area!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-11-11 13:00 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
2014-11-11 12:10 ` Fabrice Mousset | GEOCEPT GmbH
2014-11-11 13:00 ` Thomas Petazzoni [this message]
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=20141111140057.24538411@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 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.