From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory
Date: Sun, 29 Oct 2017 08:33:12 +0100 [thread overview]
Message-ID: <20171029073312.GB2899@scaer> (raw)
In-Reply-To: <1509242782-14524-1-git-send-email-f.fainelli@gmail.com>
Florian, All,
On 2017-10-28 19:06 -0700, Florian Fainelli spake thusly:
> This series allows specifying a custom kernel directory which could be an
> existing git tree. This is particularly useful when doing kernel development
> and having an existing git checkout where development is happening.
As I replied to the patch itself: this is already covered by the
opverride-srcdir mechanism, so I've marked this series as rejected in
our patchwork.
> Ideally, I would like to avoid doing the rsync operation involved with the "local" method
> and instead just have a symbolic link from /path/to/kernel -> output/build/linux.
The first rsync may take a few seconds, true, but subs=equent ones will
be much faster if all you do is change a few files, especially on a hot
directory, so there is not much gain to have with a local symlink.
OTOH, I am currently working on out-of-tree per-pacakge build, which
will (eventually) allow us to make use of the O= mechanism to build the
kernel out-of-tree, and get rid of the rsync altogether. Don't hold your
breath, though. ;-)
Regards,
Yann E. MORIN.
> Comments welcome!
>
> Florian Fainelli (2):
> pkg-generic: Don't check for trailing slashes for local method
> linux: Add support for specifying a custom directory
>
> linux/Config.in | 10 ++++++++++
> linux/linux.mk | 3 +++
> package/linux-headers/linux-headers.mk | 5 +++++
> package/pkg-generic.mk | 2 ++
> 4 files changed, 20 insertions(+)
>
> --
> 2.7.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-10-29 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 2:06 [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Florian Fainelli
2017-10-29 2:06 ` [Buildroot] [RFC 1/2] pkg-generic: Don't check for trailing slashes for local method Florian Fainelli
2017-10-29 2:06 ` [Buildroot] [RFC 2/2] linux: Add support for specifying a custom directory Florian Fainelli
2017-10-29 7:26 ` Yann E. MORIN
2017-10-29 9:12 ` Thomas Petazzoni
2017-10-29 17:26 ` Florian Fainelli
2017-10-29 18:12 ` Yann E. MORIN
2017-10-30 3:27 ` Florian Fainelli
2017-10-30 22:32 ` Yann E. MORIN
2017-11-03 5:03 ` Florian Fainelli
2017-11-03 7:04 ` Yann E. MORIN
2017-11-03 9:23 ` Thomas Petazzoni
2017-10-29 7:33 ` Yann E. MORIN [this message]
2017-10-29 17:10 ` [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Florian Fainelli
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=20171029073312.GB2899@scaer \
--to=yann.morin.1998@free.fr \
--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