>
> So, it would still be very useful to know how to link against a "libmumble.a"
> file built in another directory.
You can specify a .o file in another directory. Do you really need a .a
file? oprofile for ones does this. xfs is another example.
> Copying all sources and libraries into
> a build directory before kicking off the build is kludgey. (Linux being the
> only platform where that seems to be necessary.)
Assuming you are talking about the kernel then the kernel build system
is optimised for buiding the kernel.
And the kernel source keep relevant files together as much as possible.
See for example drivers/net. A lot of files, but most of them is a net
driver so no value gained introducing a directory for a simple driver.
And experience has shown that usage of libaries has resulted in more
problems than it has solved in most cases. Thats why libraries are so
seldom used in the kernel.
When do you need to include crc32.o in the kernel for instance.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
