Quoting Eric Pouech <[EMAIL PROTECTED]>:
> what are you actually trying to achieve ?
> 1/ port an existing DLL (or reuse its code) under Wine ?
> 2/ write a winelib app that uses an existing DLL ? (from the binary .dll
> file ?)
>
> your request ain't clear. it seems to me that you want to achieve 2,
> whereas
> you're using techniques for 1/.
I'm trying to achieve [2]. I have the Quicktime SDK for Windows from Apple,
which includes the binary qtmlclient.dll and the headers for all the functions
it contains. I want to write an application under Linux that is able to load up
this binary .dll and call assorted functions contained therein. I'm able to
compile my code (which is their win32 sample code for using the .dll for now),
but I'm confused about how to do the linking such that my calls go to the .dll.
It's my impression that I'm supposed to write a .so that serves the same purpose
an import .lib file does under Windows. I'm trying to interpret HOWTO-winelib,
but without specific code examples anywhere in the tree that do this, I'm having
a hard time. In particular, the HOWTO states:
"...In order for WineLib to use the Windows DLL, certain glue code is
needed to replace the linker magic that windows compilers use. Part of
the glue code must be written by you. The basic idea of the glue code
is that you write a new DLL that consists of function pointers. Each
function in the DLL will consist of a call on a function pointer. For
example..."
(This is followed by a code fragment that makes no sense to me.) What kind of
DLL is this that I'm writing? Is it [A] a winelib DLL that wraps calls to the
binary windows DLL? [B] a .so that wraps the calls? Who takes care of loading
up what, and how do my calls go to the Windows DLL binary? Is there an example
of this being done anywhere in the sourcetree?
Still confused,
Bret
