From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] ADEOS patch and kernel override
Date: Fri, 7 Sep 2018 13:31:21 +0200 [thread overview]
Message-ID: <20180907133121.29434851@windsurf.home> (raw)
In-Reply-To: <CAOf5uwmrFw_fKozkMn+5gVoehBig8g2PhE-ivg0GSv+PNcHfsA@mail.gmail.com>
Hello Michael,
On Fri, 7 Sep 2018 12:44:43 +0200, Michael Nazzareno Trimarchi wrote:
> I'm trying to understand if I can override the kernel and let apply
> the adeos patch on top of it. Seems that PREHOOK is not called
> in the linux kernel override directory. Is there some semantic to use?
When you said "override the kernel", I will assume you talking about
using LINUX_OVERRIDE_SRCDIR. If that is the case, then no, Buildroot
will not patch it for you.
Let me give a few more details about this, and explain why it is done
like this.
In a normal situation (i.e without OVERRIDE_SRCDIR), a package goes
through the following steps:
(1) download
(2) extract
(3) patch
(4) configure
(5) build
(6) install
When you switch to using OVERRIDE_SRCDIR for that package, the first
three steps are skipped and replaced by a "rsync" step, while the three
last steps remain the same:
(1) rsync
(2) configure
(3) build
(4) install
The reason is that if you do an override source directory:
* Buildroot has no idea what is the state of the source code in here,
so it has no idea if the patches it has will apply. Most likely not.
* More importantly, it means that you own/control the source code,
so you can simply apply whatever changes are needed on the source
code located in the OVERRIDE_SRCDIR location.
Does that help ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-07 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:44 [Buildroot] ADEOS patch and kernel override Michael Nazzareno Trimarchi
2018-09-07 11:31 ` Thomas Petazzoni [this message]
2018-09-07 12:03 ` Michael Nazzareno Trimarchi
2018-09-09 7:24 ` Michael Nazzareno Trimarchi
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=20180907133121.29434851@windsurf.home \
--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.