Dear diary, on Thu, Nov 07, 2002 at 02:22:45PM CET, I got a letter,
where Peter Samuelson [EMAIL PROTECTED] told me, that...
Remember, the whole point of HOSTCC is to support a build environment
different from the compile target - arbitrarily different, even.
I'm a bit lost here - the
Dear diary, on Wed, Nov 06, 2002 at 10:29:52PM CET, I got a letter,
where Sam Ravnborg [EMAIL PROTECTED] told me, that...
On Wed, Nov 06, 2002 at 07:52:30PM +0100, Petr Baudis wrote:
Hello,
this patch (against 2.5.46) introduces two special variables which make it
actually possible
[Petr Baudis]
Can't say anything about the C++ stuff, but the second user of shared
libraries is going to be lxdialog - hopefully this evening already,
in my patches (it already works, I'm only cleaning out few details
now; lxdialog + mconf is also user of both these extensions).
What is so
[Peter Samuelson]
Basically, what I'm saying is, I see no need for the existing .so in
the kernel build, much less another one. Static libraries are ever so
much easier to manage.
[Roman Zippel]
If you want to limit people to the config tools in the kernel, there
is indeed no need for
[Peter Samuelson]
Huh? I don't get it. How is a shared library any better than a static
library in this regard? I'm pondering the traditional advantages of
shared libraries, and I cannot think of a single one that matters here.
[Roman Zippel]
Shared libraries can be loaded
[Roman Zippel]
New features will be added and only the parser that comes with the kernel
will understand them. It's less likley that the library API will change.
Even if this is true - I'll grant you that it may be - let the vendor
package /usr/bin/qconf as a shell script that links
[Roman Zippel]
If your build environment doesn't support shared libraries, you can
easily generate a static library instead and link against it
yourself, like you described, but it's no reason to deny the
convenience to working environments.
Yeah, but until I do, I can't even run 'make
Dear diary, on Thu, Nov 07, 2002 at 02:22:45PM CET, I got a letter,
where Peter Samuelson [EMAIL PROTECTED] told me, that...
Remember, the whole point of HOSTCC is to support a build environment
different from the compile target - arbitrarily different, even.
I'm a bit lost here - the kernel
[Petr Baudis]
I'm a bit lost here - the kernel uses tons of gcc extensions - how is
another compiler supposed to understand them? And if it is
specifically extended to understand them, isn't it likely that it'll
understand the -shared switch in gcc-like way as well?
There is a difference
On Wed, Nov 06, 2002 at 07:52:30PM +0100, Petr Baudis wrote:
Hello,
this patch (against 2.5.46) introduces two special variables which make it
actually possible to have .so as the only product of build in some directory
and to link something against .so being built in another directory.
10 matches
Mail list logo
