from "makefiles.txt":
"Kbuild recognises objects used for composite objects by the suffix
-objs, and the suffix -y."
does that mean that those two suffixes are equivalent and functionally
interchangeable in a kbuild makefile?
as an example, from fs/ecryptfs/Makefile:
=====
obj-$(CONFIG_ECRYPT_FS) += ecryptfs.o
ecryptfs-objs := dentry.o file.o inode.o main.o super.o mmap.o \
read_write.o crypto.o keystore.o messaging.o netlink.o debug.o
=====
since ecryptfs can be selected as either modular or built-in, i'm
assuming that this would do the right thing in either case -- either
all of those object files would be incorporated into the loadable
module, or they would all end up built-in, right?
so in what way (if at all) does the above syntax differ from, say,
that in fs/ext3/Makefile:
=====
obj-$(CONFIG_EXT3_FS) += ext3.o
ext3-y := balloc.o bitmap.o dir.o file.o fsync.o ialloc.o inode.o \
ioctl.o namei.o super.o symlink.o hash.o resize.o ext3_jbd.o
ext3-$(CONFIG_EXT3_FS_XATTR) += xattr.o xattr_user.o xattr_trusted.o
ext3-$(CONFIG_EXT3_FS_POSIX_ACL) += acl.o
ext3-$(CONFIG_EXT3_FS_SECURITY) += xattr_security.o
=====
so why "ecryptfs-objs" versus "ext3-y"?? is there a functional
difference?
rday
p.s. also, regarding those last few lines from the ext3 Makefile,
ext3-$(CONFIG_EXT3_FS_XATTR) += xattr.o xattr_user.o xattr_trusted.o
ext3-$(CONFIG_EXT3_FS_POSIX_ACL) += acl.o
ext3-$(CONFIG_EXT3_FS_SECURITY) += xattr_security.o
i'm assuming they only make sense if the corresponding CONFIG entry is
boolean, right? as that would append to either the ext3-n or ext3-y
list. it would make no sense if one of those config choices was
tristate and selected as modular, would it? thanks.
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
