Hi, On Thu, 7 Nov 2002, Peter Samuelson wrote:
> 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 /usr/lib/qconf.o > with -lqt and $(LINUX)/scripts/kconfig/libkconfig.a . It's a little > unorthodox, but it removes the hackery of figuring out how HOSTCC is > supposed to build a shared library and whether any magic is needed at > runtime. Removes the need for the horrible stuff libtool was invented > for, in other words. > > Remember, the whole point of HOSTCC is to support a build environment > different from the compile target - arbitrarily different, even. 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. bye, Roman ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
