Thread replies: 20
Thread images: 3
Thread images: 3
Why doesn't a Win32 layer exist for POSIX, whilst there exits a POSIX layer for Windows like pic related?
If a Win32 layer was made, wouldn't that enable compiling code on POSIX written for Win32.
Would Microsoft sue the shit out of the developers if something like that was made.
A Win32 layer would enable developers to compile programs for POSIX systems, and redist them as proprietary = a shit ton of software on POSIX.
>>
Install wine
>>
What is WINE
>>
>>56649850
>>56649849
Wine is not that. Wine does that at runtime.
What I'm implying is making native Linux executables via a Win32 API (windows.h) implementation under POSIX
>>
"What is WINE"
Next, I'll take "this person is considered a massive faggot" for $500, Alex.
>>
>>56649886
No, you can compile against wine specifically as a target platform.
>>
>>56649976
https://www.winehq.org/docs/winegcc
>>
>>56649994
>>56649901
>>56649886
>>56649850
>>56649849
You don't get my point. Compiling is not the problem. The problem is that POSIX systems don't have the windows.h header and methods implemented.
>>
>>56650041
>The problem is that POSIX systems don't have the windows.h header and methods implemented.
yes they do$ ls /usr/include/wine/windows/windows.h
/usr/include/wine/windows/windows.h
$ objdump -T /usr/lib/x86_64-linux-gnu/wine/wine/kernel32.dll.so | tail -n 10
000000007b83e080 g DF .text 000000000000022c Base CreateConsoleScreenBuffer
000000007b88d0b0 g DF .text 000000000000005b Base GetWriteWatch
000000007b860ad0 g DF .text 0000000000000162 Base IsValidLanguageGroup
000000007b892c80 g DF .text 00000000000001a7 Base GetVolumePathNameA
000000007b833360 g DF .text 000000000000026b Base FindFirstChangeNotificationW
000000007b88c7a0 g DF .text 000000000000004d Base VirtualLock
000000007b872f40 g DF .text 00000000000000cc Base CreateSocketHandle
000000007b84b2e0 g DF .text 0000000000000107 Base SetFilePointerEx
>>
>>56649886
>Wine is not that. Wine does that at runtime.
WINE is more than that. Compile your linux executable with winelib to use windows.h
https://dl.winehq.org/wine/docs/en/winelib-guide.html
>>
>>56650124
Not having a space after the % in the command prompt to increase readability
Why?
>>
>>56650661
lol nobody uses spaces, % is the delimiter.
>>
>>56650661
what do you expect from the dumbest tripfag on /g/
>>
>>56649819
What exactly is the Windows-exclusive interface that you somehow wish to use on UNIX?
I am seriously concerned about your mental health,
>>
>>56652442
I don't think I've ever met a person who wasn't a fan of the Win32 API.
>>
>>56649819
Longene?
>>
>>56649819
>why does a windows-specific layer only exist on windows, while a "portable operating system interface" layer exists on many?
really makes you think
>>
>>56652479
have you gone your entire life without meeting a single person?
or do you live in microsofts' basement?
>>
>>56649819
>Why doesn't a Win32 layer exist for POSIX
because microsoft hasn't made one
only they can do it, because it's all closed and proprietary
we do have winelib, which you can build software against, this is the closest thing available to a portable win32
Thread posts: 20
Thread images: 3
Thread images: 3