From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-15 08:14:59
Felix E. Klee wrote:
> On Wednesday 15 January 2003 12:25, Vladimir Prus wrote:
>>I'm not yet successfull installing Kylix, so I can't test your changes yet,
>>but we'll integrate them asap anyway.
> It doesn't work for you? What system are you using. I'm using SuSE 8.1 and
> although the IDE isn't stable the command line tools run well.
Debian Linux. It just grabs system includes. Changes are high that I've read
only 1/10 of INSTALL file ;-) I'll try again later.
>>BTW, how shared libraries work on Kylix? In the same was as for ordinary
> Well, first of all, as you might guess, the ABI of Kylix and gcc shared C++
> library is different. Maybe that will change with version 4 of Kylix (I heard
> that the gcc 3.2 ABI is becoming some kind of standard). So, Kylix shared
> libraries cannot be linked with ld. One needs to use Kylix ilink instead (or
> maybe bc++, but I haven't tried that).
Do the need any import libraries? Or just ".so" in the linker command line?
> However, be aware that the Kylix
> generated shared libraries somehow are "unstable" and cause runtime errors
> and segfaults in applications using them. You'll find a couple of bug reports
> concering these issues on Borland's Quality Central. Note that, for whatever
> reason, static libraries seem to work flawlessly.
Cool. We have shared linking by default :-) Anyway, if shared libs are
unsuable, it's easier for us now.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk