3 ms·
Those are for DEs. For end-user application, it's a mess. You can't compile once and run everywhere. LSB (Linux Standard Base) tried to that and failed. flat
by j16sdiz 1y ago
Those are for DEs.
For end-user application, it's a mess. You can't compile once and run everywhere.
LSB (Linux Standard Base) tried to that and failed.
flatpak/Snap/AppImage all tried to that, each have its own set of problems.
- LtWorf 1y agoCan you compile on windows11 and run it on windows xp? Yeah didn't think so
- int_19h 1y agoYou can do this even with the official Microsoft SDKs (just need to have the XP targeting pack). And then there are numerous third party development tools that allow this.
- LtWorf 1y agoYou can do this on linux too, make a chroot, done.
- freeone3000 1y agoWindows doesn’t need a chroot and a separate install base. You can build one binary for Longhorn, using the Windows 11 SDK, and it will run on everything from NT4 to 11 without modification.
- LtWorf 1y ago*assuming you wrote it in such a way to be able to do it
- int_19h 1y agoYeah, and then hope that the tools that you need to build even run on some ancient glibc version.
- LtWorf 1y agoStuff like innosetup?
- pjc50 1y agoUnless you choose to use APIs that aren't in Windows XP, then this isn't a problem. Win32 backwards compatibility is very impressive. Building a Win16 application would be more difficult. But this isn't directly comparable. The issue with Linux is getting a precompiled binary to work properly across all currently up to date distributions.
- const_cast 1y ago> For end-user application, it's a mess. You can't compile once and run everywhere. Yes you can, you said it yourself: flatpak, snap, and appimage. Okay okay, those technologies have problems. But all technologies do. That's why Microsoft has half a dozen GUI frameworks and then they build their own in-house applications in Electron :P