For one this winudf is compiled with https://openwatcom.org/ which targets older C89/C99 and legacy C++ standards alongside legacy platforms (DOS, OS/2, Win16/Win32). So unlikely direct reuse would help
ale42 3 hours ago [-]
Plus 16-bit segmented code. The code contains explicit "FAR" declaration for pointers, etc... when taking "outside" code to such an environment, extensive changes might be required.
AshamedCaptain 2 hours ago [-]
Which is kind of the pointless since A) By being >100KB of _conventional_ memory this is practically useless for all DOS platforms, B) You have gcc-ia16 for those anyway if you wanted to for bragging rights or whatever , C) for 9x and above you can already use normal gcc.
Watcom also has terrible licensing up to the point it is up for debate whether you can really publish anything with it that's not also using Watcom license.
We all know the real reason is that this is just AI slop.
hn_submit 1 hours ago [-]
Because the author never wrote it since it's slop?
Fergusonb 11 minutes ago [-]
I feel like it makes more sense to reskin a modern linux distro than to add blue ray support to these operating systems?
I really wish the use-case was included, are they trying to show movies while doing cat scans on a machine that can only run windows 98? Just the love of the game?
So many questions about this answer to a very specific problem.
londons_explore 2 hours ago [-]
Next time I need a blueray on Windows 1.0, now I know where to look!
[1]https://code.videolan.org/videolan/libudfread
Watcom also has terrible licensing up to the point it is up for debate whether you can really publish anything with it that's not also using Watcom license.
We all know the real reason is that this is just AI slop.
I really wish the use-case was included, are they trying to show movies while doing cat scans on a machine that can only run windows 98? Just the love of the game?
So many questions about this answer to a very specific problem.