Porting Windows Dynamic Link Libraries to Linux
1–10 of 44 posts
Re: Porting Windows Dynamic Link Libraries to Linux
#2why?
Re: Porting Windows Dynamic Link Libraries to Linux
#3why?
That's answered in the README.
Re: Porting Windows Dynamic Link Libraries to Linux
#4why?
...why not?
Re: Porting Windows Dynamic Link Libraries to Linux
#5Very cool, to load .dll, so tests/builds/packaging can be run in Linux. There is also the possibility of signing .exe/.dll on Linux. AFAIK, the remaining stuff is to sign .msi files.
Re: Porting Windows Dynamic Link Libraries to Linux
#6Why not just use full-on WINE? The basic system calls are pretty much fully covered. It seems this duplicates a lot of work.
Re: Porting Windows Dynamic Link Libraries to Linux
#7Why not just use full-on WINE? The basic system calls are pretty much fully covered. It seems this duplicates a lot of work.
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.
Re: Porting Windows Dynamic Link Libraries to Linux
#8[deleted]
Re: Porting Windows Dynamic Link Libraries to Linux
#9Re: Porting Windows Dynamic Link Libraries to Linux
#10This reminds me of a tool Jeff Roberts wrote at RAD Game Tools which would repackage libraries so they were loadable on Linux. At the time the motivation was that MSVC was generating much better code than GCC for Bink, so he'd compile on Windows with MSVC and cross-link to Linux with his custom tool.