Re: [jamboost] Toolset inheritance, Kylix

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

Felix E. Klee wrote:
> On Wednesday 22 January 2003 08:03 am, Vladimir Prus wrote:
> 
>>>BTW, I'll test it with QT once the QT stuff works fine with gcc.
>>
>>Hopefully you're able to do it now.
> 
> 
> Just tried it. Unfortunately, it doesn't work:
> bc++ -v -q -ebin/kylix/debug/main-target-hello/hello 
> bin/kylix/debug/main-target-hello/main.o
> bin/kylix/debug/main-target-hello/hello_world_widget.o
> bin/kylix/debug/main-target-hello/moc_hello_world_widget.o 
> 
> Error: Unresolved external 'QApplication::~QApplication()' referenced from 
> bin/kylix/debug/main-target-hello/main.o
> 
> Obviously, the linker command line is incomplete: the -L option and the QT 
> library are missing. 

Right, the borland toolset is slighly out-of-date, so it silently ignored
some properties. Hopefully, an active user of Kylix toolset will help to
find other bugs ;-)

> Here is something that works:
> bc++ -v -q -L$QTDIR/lib -ebin/kylix/debug/main-target-hello/hello 
> bin/kylix/debug/main-target-hello/main.o 
> bin/kylix/debug/main-target-hello/hello_world_widget.o
> bin/kylix/debug/main-target-hello/moc_hello_world_widget.o 
> libqt.so
> 
> As you see, I didn't use "-lqt" because that doesn't work. According to the 
> bc++ documentation, "-l" does something else:

Eh... does that exactly "libqt.so"? Is that library searched in -L path? Or it 
should be present in "."?

In either case, I've made the changes to get both "-L" and "libqt-mt.so" into
bc++ command line. Could you please test again?

> -lx Pass option x to linker
> -l-x Disable option x for linker
> So, I don't know if there's a better way to specify libraries. Makefiles 
> generated by the Kylix IDE actually contain calls to ilink where the 
> libraries are also specified by their complete file name. As a reminder, 
> here's an excerpt from a Kylix generated Makefile that I send to you in a 
> previous email:
> ilink \ 
> -Tpd -aa -D"" -x -Gn -v \
> -Ltmp:/Net/hubble/Users/felix/local/lib/kylix3//lib/obj \
> -L/Net/hubble/Users/felix/local/lib/kylix3//lib:/usr/lib:/lib \
> -L/usr/X11R6/lib:/Net/hubble/Users/felix/local/lib/kylix3//bin \
> borinitso.o foo.o, libfoo.so,, \
> libborcrtl.so libborstl.so libborunwind.so libc.so libm.so libdl.so,, \
> foo.res

I don't really know what should be used. Borland/Kylix users should decide.

- Volodya