On: Porting Windows Dynamic Link Libraries to Linux

[_fq4v]

Why not just use full-on WINE? The basic system calls are pretty much fully covered. It seems this duplicates a lot of work.

[SA500 → _fq4v]

'This project does not replace Wine or Winelib.

Winelib is used to port Windows C++ projects to Linux, and Wine is intended to run full Windows applications. This project is intended to allow native Linux code to load simple Windows DLLs.

The closest analogy would be ndiswrapper but for userspace.'

[Arnavion → _fq4v]

Are the Windows API implementations of WINE usable by a native Linux program (eg as a library of some sort)? That seems to be the requirement here.

[snarfy → Arnavion]

Yes, I've written a windows dll loader for linux based on wine myself. It's fairly simple to add support for LoadLibrary() and GetProcAddress() to a linux program using wine libraries.

[chrisseaton → Arnavion]

Yes - using WINE as a library is one way of porting to Linux.

[_fq4v → Arnavion]

WINE's had this ability for more than a decade -- see winelib.