@whitequark I might have used one, actually - but it was very very bad-dirty, linking the 3D package into our engine to access their file formats, using multiple versions of image processing libraries at the same time kind-of-stuff…
@whitequark this reminds me of when i tried to cross compile windows openmw from linux and was having difficulties with linking and eventually had a 2GB executable which had the whole Qt framework statically linked in
@scherzog this is funny to hear considering that monomorphization, which plagues certain kinds of rust code, is already a problem for c++ that is extensively used in windows
@whitequark or one giant ELF file.
And also: a Linux distro with everything inside a giant PE file (as far as I understand, Linux already can do that for the kernel so that BIOS loads it as a bootloader)
@whitequark@dalias Oh, wait, I just thought a thought. Does /usr/bin/wine basically play the same role as /lib64/ld_linux_x86_64.so.2, just for PE files instead of ELF files?
Add comment