From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] kbuild: Document lib-y
Date: Sun, 8 Jun 2003 20:01:13 +0200 [thread overview]
Message-ID: <20030608180113.GA3987@mars.ravnborg.org> (raw)
Hi Linus, documentation for the newly added lib-y.
Sam
===== Documentation/kbuild/makefiles.txt 1.8 vs edited =====
--- 1.8/Documentation/kbuild/makefiles.txt Sun Mar 16 06:52:28 2003
+++ edited/Documentation/kbuild/makefiles.txt Sun Jun 8 19:55:25 2003
@@ -11,7 +11,7 @@
--- 3.2 Built-in object goals - obj-y
--- 3.3 Loadable module goals - obj-m
--- 3.4 Objects which export symbols
- --- 3.5 Library file goals - L_TARGET
+ --- 3.5 Library file goals - lib-y
--- 3.6 Descending down in directories
--- 3.7 Compilation flags
--- 3.8 Command line dependency
@@ -214,20 +214,33 @@
modules exporting symbols.
See also Documentation/modules.txt.
---- 3.5 Library file goals - L_TARGET
+--- 3.5 Library file goals - lib-y
- Instead of building a built-in.o file, you may also
- build an archive which again contains objects listed in $(obj-y).
- This is normally not necessary and only used in lib/ and
- arch/$(ARCH)/lib directories.
- Only the name lib.a is allowed.
+ Objects listed with obj-* is used for modules or
+ are combined in a built-in.o for that specific directory.
+ There is also the possibility to list objects that will
+ be included in a library, lib.a.
+ All objects listed with lib-y are combined in a single
+ library for that directory.
+ Objects that are listed in obj-y and additional listed in
+ lib-y will not be included in the library, since they will anyway
+ be accessible.
+ For consistency objects listed in lib-m will be included in lib.a.
+
+ Note that the same kbuild makefile may list files to be built-in
+ and to be part of a library. Therefore the same directory
+ may contain both a built-in.o and a lib.a file.
Example:
#arch/i386/lib/Makefile
- L_TARGET := lib.a
- obj-y := checksum.o delay.o
+ lib-y := checksum.o delay.o
This will create a library lib.a based on checksum.o and delay.o.
+ For kbuild to actually recognize that there is a lib.a being build
+ the directory shall be listed in libs-y.
+ See also "6.3 List directories to visit when descending".
+
+ Usage of lib-y is normally restricted to lib/ and arch/*/lib.
--- 3.6 Descending down in directories
@@ -727,7 +740,7 @@
head-y, init-y, core-y, libs-y, drivers-y, net-y
$(head-y) list objects to be linked first in vmlinux.
- $(libs-y) list directories where a libs.a archive can be located.
+ $(libs-y) list directories where a lib.a archive can be located.
The rest list directories where a built-in.o object file can be located.
$(init-y) objects will be located after $(head-y).
next reply other threads:[~2003-06-08 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 18:01 Sam Ravnborg [this message]
2003-06-17 22:16 ` Riley Williams
2003-06-21 6:21 ` Sam Ravnborg
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=20030608180113.GA3987@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®