On Wed, 2005-11-02 at 18:28 +0900, Mike McCormack wrote:
Daniel Stodden wrote:
though, there's not much application code yet, except a small test program written by myself, currently only meant to call a single function on the dll.
so, using winemaker does not seem to spit out anything usable, and there seems to be no official documentation on how to use winebuild here.
Why not just use LoadLibrary("vendor.dll") and GetProcAddress() in you winelib application instead of mucking round with winegcc and winebuild in order to directly link your dll?
you're right. as i said, that's an obvious option.
but since linking directly would work on windows and since the .def-mechanism with wine tools is supposed to support just that, and since, for the purpose in question, i really don't see the point in programming the dynamic loader manually, why not give it a try as well?
but basically you're right.
regards, daniel