Re: Tcl extensions built with lcc-win32
- From: EL <eckhardnospam@xxxxxx>
- Date: Wed, 30 Apr 2008 17:52:14 +0200
Olaf Dietrich schrieb:
I could build and load my extension, but only when linking with the
non-stubs libraries (tcl85.[lib|dll], tk85.[lib|dll]). However, I was not
able to build a version of the extension using the Tcl stubs mechanism,
i.e. linking with the tclstub85.lib library (which I also transformed
to the lcc format). The dll of my extension is built without any
errors or warnings, but when I attempt to load the extension, Tcl
complains:
Tclstubs is a mechanism to load extensions without the OS library loader, or at least with much less interaction. The "tclStubsPtr" that you see in your dumpbin output contains addresses of functions in tcl.dll (I believe) which are resolved by the stubs mechanism at runtime.
Lcc seems to produces binaries that can not track down these function pointers. I suggest you the following:
a) compile Tcl and Tk with LCC and try these binaries for compiling your extension
b) just use MSVC. It also works with msys/gcc.
--
Eckhard
.
- Follow-Ups:
- Re: Tcl extensions built with lcc-win32
- From: Olaf Dietrich
- Re: Tcl extensions built with lcc-win32
- References:
- Tcl extensions built with lcc-win32
- From: Olaf Dietrich
- Tcl extensions built with lcc-win32
- Prev by Date: Re: Tk programming challenge
- Next by Date: tkimg OS X universal
- Previous by thread: Tcl extensions built with lcc-win32
- Next by thread: Re: Tcl extensions built with lcc-win32
- Index(es):
Relevant Pages
|