DLL's ; Import libs ; def files etc ..
J D L
De_Laender-De_Winter@village.uunet.be
Sat May 20 22:47:00 GMT 2000
Earnie Boyd wrote:
>
> --- J D L <De_Laender-De_Winter@village.uunet.be> wrote:
> -8<-
> > I have a database program, distributed as an DLL.
> > The distribution contains also import libraries for
> > the Borland compiler and the Microsoft compiler.
> > On top of that it even contains a .DEF file, however with
> > following constructs in it :
> >
> > EXPORTS
> > _SQLAllocConnect@8
> > _SQLAllocConnect = _SQLAllocConnect@8
> >
> > I created a 'cygnus' def file with the usual manipulations out of
> > the FAQ.
> >
> -8<-
>
> Why didn't you use the supplied .def file to create the import library??? By
> creating your own you missed the aliases that were in the supplied .DEF file
> that caused your problems.
>
I hoped it was that simple ...
Apart from stopping on some syntax errors before the 'EXPORTS' section
(that I corrected by removing most lines before EXPORTS) :
1) If I keep only the SQLAllocConnect@8 then linking goes OK, but
at runtime : linked against not existing SQLAllocConnect@8
2) If I keep only SQLAllocConnect, then linking fails ...
3) If I keep the whole stuff, then the same as 1.
My (restricted knowledge) is :
1) the object code calls _SQLAllocConnect@8 (just by construct :
function f -> _f@stacksize)
2) The import library MUST have this function in it. So in my case
_SQLAllocConnect@8 must be in the import
3) The DLL expects _SQLAllocConnect as function call, which
is proven by my manipulation via assembly. Changing the _f@ by _f
does really the job !
4) Somewhere the equivalence between both should be declared
but how and where in cygnus' environment ???? The .DEF file ???
Thanks for all explanation/help !
Jos
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
More information about the Cygwin
mailing list