From: John Weber <rjohnweber@gmail.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Linux kernel recipe override question
Date: Mon, 24 Feb 2014 13:51:26 -0600 [thread overview]
Message-ID: <530BA2BE.7060502@gmail.com> (raw)
Here is a question someone might be able to quickly answer.
I want to be able to override the SRCREV, SRCBRANCH, and the git repository for
the kernel recipe in local.conf. I like to do this so that I can do local
hacking on a kernel without having to edit the recipe files themselves, and I
find that managing local.conf is easier when I'm changing SRCREVs a lot.
I've been able to override SRCBRANCH by doing this:
In recipes-kernel/linux/linux-wandboard.inc:
SRCBRANCH ??= "master"
The default is set in recipes-kernel/linux/linux-wandboard_3.10.17.bb:
SRCBRANCH ?= "<the-default-branch>"
Then, in local.conf, I can override it:
SRCBRANCH_linux-wandboard = "<my-local-hacking-branch>"
This works fine for SRCBRANCH. If I do the same thing with SRCREV, it doesn't
seem to work. I've done this:
In linux-wandboard_3.10.17.bb:
SRCREV ??= "<default big long commit id>"
In local.conf:
SRCREV_linux-wandboard = "<my local branch commit id>"
I always get the checkout of the SRCREV assignment done in the recipe file, not
the one I set in local.conf.
Any idea why? The only thing I can think of is that SRCREV is evaluated completely before
local.conf settings are evaluated.
John
next reply other threads:[~2014-02-24 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 19:51 John Weber [this message]
2014-02-24 20:05 ` Linux kernel recipe override question Gary Thomas
2014-02-25 12:11 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2014-02-24 20:27 Robin Findley
2014-02-25 3:59 ` John Weber
2014-02-25 12:20 ` Otavio Salvador
2014-02-25 14:52 ` John Weber
2014-02-25 15:34 ` Otavio Salvador
2014-02-25 15:53 ` John Weber
2014-02-25 15:57 ` Gary Thomas
2014-02-25 16:39 ` Otavio Salvador
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=530BA2BE.7060502@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.org \
/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.