From: matt mooney <mfm@muteddisk.com>
To: Michal Marek <mmarek@suse.cz>, Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [PATCH] Documentation/kbuild: correct variable definitions in makefiles.txt
Date: Sun, 19 Sep 2010 23:33:32 -0700 [thread overview]
Message-ID: <1284964412-32211-1-git-send-email-mfm@muteddisk.com> (raw)
Change $(src) and $(obj) definitions to state the path as absolute and
not relative.
Signed-off-by: matt mooney <mfm@muteddisk.com>
---
Hmm, this file is also _full_ of bad grammar and might be out of date FAIK.
If you would like it updated/corrected, please let me know. I don't mind doing
this, but only if it is beneficial and wanted.
Documentation/kbuild/makefiles.txt | 11 +++++------
1 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/Documentation/kbuild/makefiles.txt b/Documentation/kbuild/makefiles.txt
index c787ae5..fe162f5 100644
--- a/Documentation/kbuild/makefiles.txt
+++ b/Documentation/kbuild/makefiles.txt
@@ -376,14 +376,13 @@ more details, with real examples.
Two variables are used when defining special rules:
$(src)
- $(src) is a relative path which points to the directory
- where the Makefile is located. Always use $(src) when
- referring to files located in the src tree.
+ The absolute path to the directory where the makefile is
+ located. Always use $(src) when referring to files located
+ in the src directory.
$(obj)
- $(obj) is a relative path which points to the directory
- where the target is saved. Always use $(obj) when
- referring to generated files.
+ The absolute path to the directory where the target is saved.
+ Always use $(obj) when referring to generated files.
Example:
#drivers/scsi/Makefile
--
1.7.2.1
next reply other threads:[~2010-09-20 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 6:33 matt mooney [this message]
2010-09-29 15:03 ` [PATCH] Documentation/kbuild: correct variable definitions in makefiles.txt Michal Marek
2010-09-29 17:50 ` Sam Ravnborg
2010-09-29 23:19 ` matt mooney
2010-10-01 20:56 ` Michal Marek
2010-10-02 4:14 ` matt mooney
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=1284964412-32211-1-git-send-email-mfm@muteddisk.com \
--to=mfm@muteddisk.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@xenotime.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