Seeing other wine tools like winemaker, winebuild, and winegcc and learning about winelib, I have a few questions about them.

Firstly, when I saw winelib's description, I thought it totally converted win32 apps into raw unix apps, and I thought, "Great! No more slow apps, I would rather invest some time compiling an entire library of a game's dlls and executables then run it through wine/winex and get a slower or buggy performance". Then I learnt it was for each single app, and I think they convert it, byte by byte into raw Unix apps.

However, I do not get these tools like winemaker and winebuild. What exactly do they do? Winemaker says something like to convert c source files into something suitable to link to winelib. I think to myself, "hmm...so it can easily (or at least better than byte by byte) be done". I still don't get it, why can't you just convert a windows c source file to a Unix compatible one using winelib? Winebuild looks interesting, I tried it on several windows executables, and I thought it was the C++ decompilation rendering of them, but then I realise they are suspiciously similar. It would be quite useful though, if I could actually decompile win32 binary applications into C++ source files. There are several other tools like winegcc, etc.

I don't get most of it though, someone enlighten me?

Also for WineX, can someone help me? I keep getting access violation errors running most games. And then, many games also won't detect their dependency dll's and config files raw, I used to bypass this using progman, but when I reinstalled into slackware, it now says no application is associated with them as though they were like documents or data files instead of executables.

Bump