Re: [jamboost] Re: Kylix support

From: Felix E. Klee (felix.klee.jamboost_at_[hidden])
Date: 2003-01-16 04:48:52

On Thursday 16 January 2003 09:53 am, Vladimir Prus wrote:
> >>Do the need any import libraries? Or just ".so" in the linker command
> >> line?
> >
> > I'm not sure whether I understand what you mean. Here's an example for an
> > ilink invocation to create a shared object:
> >
> > 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
> >
> > The above lines come straight from Kylix. I created a new shared object
> > project called foo and exported the corresponding Makefile using the
> > "Project->Export Makefile" menu item in the IDE. Then I called "make -f
> > foo.mak" and copied and beautified the lines showing the ilink
> > invocation.
>
> OK, I see "so" files in command line and that what I was asking for. On
> Windows, you'd have to create "import library" from DLL and use the import
> library on the linker command line. That's additional complexity.

I see. There's one thing, however, that I forgot to mention. Classes, 
functions and data needs to be exported using the __declspec(dllexport) 
keyword in the source. This seems to be the same behavior as under Windows. 
Of course, that's only relevant for the authors of shared libraries, not for 
the Boost Build system.

Felix

-- 
To contact me personally don't reply but send email to 
felix DOT klee AT inka DOT de