From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Create a symbolic link to the target kernel directory.
Date: Thu, 01 Nov 2012 02:07:49 +0100 [thread overview]
Message-ID: <5091CB65.8070409@mind.be> (raw)
In-Reply-To: <1351729065-31324-1-git-send-email-sagaert.johan@skynet.be>
On 11/01/12 01:17, Sagaert Johan wrote:
> This symbolic link makes it easier when building kernel modules.
> The makefile for a module no longer has to point to the full directory name of the kernel but can use this symbolic link instead.
> You no longer need to edit the path to the kernel tree in the module's makefiles when changing your target kernel version.
I don't see the point... What's wrong with passing KERNELDIR=$(LINUX_DIR) to
the sub-make in the .mk file? Cfr. lttng-modules.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-01 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 0:17 [Buildroot] [PATCH 1/1] Create a symbolic link to the target kernel directory Sagaert Johan
2012-11-01 1:07 ` Arnout Vandecappelle [this message]
2012-11-01 1:14 ` Sagaert Johan
2012-11-01 9:19 ` Thomas Petazzoni
2012-11-01 19:10 ` [Buildroot] [PATCH 1/1] Create a symbolic link to the target kernel directory. example Sagaert Johan
2012-11-01 22:24 ` Thomas Petazzoni
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=5091CB65.8070409@mind.be \
--to=arnout@mind.be \
--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.