[Wine] Re: Problems creating a winelib-based program

[Daniel Skorka]

Fleabag <madparrott at gmail.com> wrote:
> As a proof of concept, I have started small. I wrote a simple Windows
> DLL with an exported function which returns a string, and built it on
> my Windows PC. I wrote a OS X program (source code is in
> "simpleapp.cpp") which loads the DLL (using LoadLibrary), locates the
> function (using GetProcAddress), calls the function and displays the
> string to stdout.

I do not quite understand. If this program uses the Win32 API and will
be compiled using winelib, why do you call it an "OS X program"?

> I used winemaker to generate the Makefile, then built it using make.
> This automatically linked the executable with winelib. The result is a
> file called "simpleapp.exe.so". It does execute and function as
> expected, BUT, unfortunately cannot be run standalone, it seems it
> *has* to be launched using "wine simpleapp.exe.so". If I try to run
> simply "./simpleapp.exe.so" then I get the message "Bad program (or
> shared library)".

As I see it, you want a library and not a standalone executable. What
happens if you tell your application to use simpleapp.exe.so as a
plugin?

Daniel