From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Out of tree Linux kernel builds?
Date: Tue, 6 Nov 2018 08:45:34 +0100 [thread overview]
Message-ID: <20181106084534.08bc72ca@windsurf> (raw)
In-Reply-To: <02530ea6-3942-3fe1-91b8-9040e3838972@gmail.com>
Hello Florian,
On Mon, 5 Nov 2018 16:08:05 -0800, Florian Fainelli wrote:
> AFAIR a while back you mentioned that you were looking into adding
> support for out of tree Linux builds. Do you have working patches for
> that, or you would rather have someone take a stab at doing it?
In fact we are not planning on supporting out of tree kernel builds,
but rather to support out of tree build for all packages in a generic
way, which would include the 'linux' package of course.
I did some work in this area many years ago, Yann picked up some of the
work, see the current status at
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/oot.
I see he has other "oot" branches, such as
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/oot-build-dir,
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/oot-libtool
and
https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/oot-same-source.
I'm not sure how they relate to each other (I haven't looked at the
patches).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-06 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 0:08 [Buildroot] Out of tree Linux kernel builds? Florian Fainelli
2018-11-06 4:35 ` Baruch Siach
2018-11-06 4:44 ` Florian Fainelli
2018-11-06 7:45 ` Thomas Petazzoni [this message]
2018-11-06 21:10 ` Yann E. MORIN
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=20181106084534.08bc72ca@windsurf \
--to=thomas.petazzoni@bootlin.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.