From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alan Martinovic <Alan.Martinovic@zenitel.com>
Subject: Re: [ptxdist] Modifing platform rules
Date: Wed, 24 Sep 2014 13:53:13 +0200 [thread overview]
Message-ID: <201409241353.13365.jbe@pengutronix.de> (raw)
In-Reply-To: <916A03CCEB30DF44AD98D4CFDC7448D00D59BAD8@nooslzsmx1.zenitelcss.com>
Hi Alan,
On Wednesday 24 September 2014 10:30:36 Alan Martinovic wrote:
> I'm trying to get use the kernel from an external source (git repository).
> The chapter 6.1. defines this how to do this, however it doesn't suite me
> because it requires additional manual work for someone setting up the build
> system.
>
> I know how to write the .make and .in file for the kernel but in the
> userpace configuration (creating kernel.in and kernel.make in /rules) but
> that would completely ignore the kernel platform settings which I don't
> believe is the intended way.
>
> What is the proper way to extend the platform rules and .in files?
Do it in the platform. But the folder names differ. The *.make files should be
still in the rules/ directory inside the platform directory, but the
corresponding *.in file must be located in the platforms/ directory.
So, if your platform is located in configs/platform-myboard/ the kernel rules
must be located in:
configs/platform-myboard/platforms/kernel.in
configs/platform-myboard/rules/kernel.make
Happy hacking
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-09-24 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 8:30 Alan Martinovic
2014-09-24 11:53 ` Juergen Borleis [this message]
2014-10-05 13:16 ` Alan Martinovic
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=201409241353.13365.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=Alan.Martinovic@zenitel.com \
--cc=ptxdist@pengutronix.de \
/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