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 14:23:04 +0200 [thread overview]
Message-ID: <20170503142304.07002af5@free-electrons.com> (raw)
In-Reply-To: <60824eaa-5a38-a9b7-1394-ae9c5d2a64bf@free.fr>
Hello,
On Wed, 3 May 2017 11:48:28 +0200, Mason wrote:
> > What do you call "its own build system" ?
>
> A scary jungle of intertwined / recursive Makefiles. Basically,
> one types 'make all' to build modules, libs, apps, and firmwares.
> Sorting this mess out would be a multi-man-months effort.
You don't need to "sort this mess out". Just create a Buildroot package
that does "make all".
> > Create Buildroot packages for the different software components you
> > need to build.
>
> OK, what's the second best way to do this, then?
Again: create a package for it. Whatever you think should be done in a
shell script can be done in a Buildroot package, so there is no reason
to not create a Buildroot package for your stuff.
You don't necessarily need to split it into multiple Buildroot
packages. It can be just one big Buildroot package that calls your
"make all" stuff to build your home-grown apps/libs/modules in one go.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-03 12:23 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
2017-05-03 9:48 ` Mason
2017-05-03 12:23 ` 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=20170503142304.07002af5@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