Re: [jamboost] Toolset inheritance, Kylix

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-23 10:35:15

Felix E. Klee wrote:

>>Ick! What does it say if you specify "libbar.a" in the linker commnad line
>>(but don't change the name of the actual library?)
> 
> 
> Fatal: Unable to open file 'libbar.a'
> 
> BTW, I just tried "-L../kylix-lib-test" but it still can't find bar.a if 
> either "bar.a" or "libbar.a" is specified.

Bad.

> It probably looks only in $(BCB)/lib and in the current directory for static 
> libraries and ignores the -L option. To make sure that the problem is not 
> caused by bar.a itself, I just moved $(BCB)/lib/libborcrtl* to 
> ../kylix-lib-test and now I get (with -L correctly set, of course)
> Fatal: Unable to open file 'libborcrtl.a'
> I probably should report this as a bug to Quality Central.

Probably. BTW, since you noted that use Kylix because of compile speed,
you may be interested to know that CVS HEAD of gcc now contains support for 
precompiled headers:

http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html

Hopefully we'd get some speedup when that feature is available in
released version, but that's not very soon, at all events.

>>>Yes, it works now. However, I had to change qt-mt into qt in new/qt.jam
>>>since I didn't try to compile the multi threaded QT library for Kylix
>>>yet. Shouldn't qt be the default and only be changed to qt-mt when
>>><threading> is set to multi?
>>
>>You've right! Care to try fixing that? The add-properties rule in qt.jam is
>>the key: just compute the library name depending on whether <theading>multi
>>is in properties.
> 
> 
> OK, I'll try it, but probably not today; tomorrow evening is more likely.

OK. Good luck.

- Volodya