From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps
Date: Wed, 3 May 2017 11:35:09 +0200 [thread overview]
Message-ID: <20170503113509.0d5cd238@free-electrons.com> (raw)
In-Reply-To: <4e87c694-21a2-7f06-9d88-f736e832e061@free.fr>
Hello,
On Wed, 3 May 2017 11:15:15 +0200, Mason wrote:
> I use buildroot to generate kernel + rootfs image for an ARM
> platform, typically cross-compiled with the Linaro toolchain.
>
> I also have a large body of software in a separate repo
> (outside of the BR tree) with its own build system.
What do you call "its own build system" ?
> This repo includes kernel modules, user-space libraries
> and apps, which need to be cross-compiled and built on
> top of the rootfs generated by BR.
>
> Therefore, I would need to pass some information from BR
> to the separate build system, such as
>
> - ARCH
> - CROSS_COMPILE
> - location of the cross-toolchain, to add to the PATH
> - location of the sysroot
>
> What is the best way to do this?
Create Buildroot packages for the different software components you
need to build.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-03 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 9:15 [Buildroot] Cross-compiling out-of-tree kernel modules and user-space apps Mason
2017-05-03 9:35 ` Thomas Petazzoni [this message]
2017-05-03 9:48 ` Mason
2017-05-03 12:23 ` 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=20170503113509.0d5cd238@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