From: Stefan v. Wachter <svwa@iw...> - 2002-11-29 14:40:08
Thanks for the answers! I integrated VXL in a dll which is a extension
to the tcl/tk scripting language. I encountered problems when I tried
to link my dll with the vxl libs
("MSVCRT.lib (MSVCRT.dll): error LNK2005: _abort already defined in
LIBCC.lib (abort.obj)" and more like this). Finally I added the
vxl-sources (beta1) directly to my dll project. So I can use vxl, but
it is a little bit inconvenient.
It should be possible to add static libraries like the vxl libs to a
dll project, but this fails with vxl.
I didn't yet try to build vxl dlls with the cygwin tools as suggested,
because I was a little bit sceptical wether cygwin generated .so files
would be compatible with VisualStudio 6 dlls. But I wouldn't mind if it
If it is necessary I think I could spend some time to make the changes
necessary to generate real dlls.
From: Peter Vanroose <Peter.V<anroose@es...> - 2002-11-29 16:27:34
> If it is necessary I think I could spend some time to make the changes
> necessary to generate real dlls.
It's relatively straightforward, although probably time consuming.
There is already a first attempt in e.g. the vbl library directory:
There is even a script (bin/vxl_make_dll_h.pl) to create such a file.
The file vbl/dll.h is included (and used) in vbl/vbl_ref_count.h only;
it declares the static data member verbosity_ as data to be exported.
I've no idea if this is sufficient to create a working .dll; I have
a vague memory of the need of _declspec(dllexport) to replace
_declspec(dllimport) when *using* the variable to be exported,
and that it also may be necessary on *functions* (in addition to
Get latest updates about Open Source Projects, Conferences and News.