From: Sam Ravnborg <sam@ravnborg.org>
To: Bruce Korb <bruce.korb@gmail.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: missing build functionality?
Date: Thu, 10 Nov 2005 22:09:56 +0100 [thread overview]
Message-ID: <20051110210956.GD7584@mars.ravnborg.org> (raw)
In-Reply-To: <200511100807.53219.bruce.korb@gmail.com>
>
> 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
prev parent reply other threads:[~2005-11-10 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 20:33 missing build functionality? Bruce Korb
2004-11-23 21:02 ` Valdis.Kletnieks
2005-11-10 16:07 ` Bruce Korb
2005-11-10 21:09 ` Sam Ravnborg [this message]
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=20051110210956.GD7584@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bruce.korb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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