On Thu, 12 Feb 2004, Chris Seaton wrote:
Hmmm... I wasn't aware of winegcc (the tutorial doesn't mention it). Do I have to use winegcc? The script it generates seems to use wine, but I thought winelib could be used independantly of wine.
You don't have to use winegcc, but you only gain complexity if you don't. Your winelib app will still have to use wine, it can't be made independant of wine ATM.
Is it not possible to generate a normal, single file binary that simply uses winelib to provide the Windows API functions?
No. This is a long discussion, please search the archives. Bottom line is that you can't, and this will likely not change in the near future.
Using winegcc -mwindows did solve my problem, but now I can't use GDB on my program because it's in a DLL that I can't start in GDB, that's why I don't like the wrapper script.
It generates a shell script that launches the .exe.so that it creates. Use winegdb on this one instead.