BSD on Windows: Things I wish I knew existed • Hacker News Board

Re: BSD on Windows: Things I wish I knew existed

#111

Post by rollcat » Tue, Dec 12, 2023, 3:38 PM UTC

xorcist wrote: post #105

rollcat wrote: post #81

Earlier quoted context omitted.

The love2d static build story was a tangent to my 2016 challenge to ship one game every month of the year. The tangent ended up delaying the March game indefinitely, and thus ending the challenge... My memory is a bit hazy, so apologies for the scarce/imprecise details. I really, really wanted to ship binary builds for the three major platforms: Windows, Mac, and Linux; so that my friends and strangers could actually…

Just ship the .so files? It's what most commercial software and things like Firefox do. Just run it via a wrapper that sets LD_PRELOAD.

I have my eyes on AppImage - it looks the most sane, vs Flatpak or Snap. For CLI apps, Go is great at making static binaries that Just Work.

Most of my past interactions with LD_PRELOAD caused some trouble down the line. It likes to leak into unexpected places, sowing discord and heisenbugs. I'd rather never touch it again unless out of other options.

Re: BSD on Windows: Things I wish I knew existed

#112

Post by rollcat » Tue, Dec 12, 2023, 3:42 PM UTC

pjmlp wrote: post #103

rollcat wrote: post #81

Earlier quoted context omitted.

The love2d static build story was a tangent to my 2016 challenge to ship one game every month of the year. The tangent ended up delaying the March game indefinitely, and thus ending the challenge... My memory is a bit hazy, so apologies for the scarce/imprecise details. I really, really wanted to ship binary builds for the three major platforms: Windows, Mac, and Linux; so that my friends and strangers could actually…

I was recently surprised that CGO only works on Windows with a msys2 compiler, while everyone else works just fine with Visual C++, or VS provided clang.

I'm yet to tackle actually testing any of my software on a real Windows machine; I usually just smoke-test things through Wine. (That's already more effort than what Linux devs do towards BSD so I award myself a point for that.)

Re: BSD on Windows: Things I wish I knew existed

#113

Post by Projectiboga » Tue, Dec 12, 2023, 3:59 PM UTC

rollcat wrote: post #81

zlg_codes wrote: post #71

Earlier quoted context omitted.

This is relevant to my interests. What roadblocks did you run into when you attempted to build statically? I assume your goal was to have a single binary of Love2D so you can swap it around and not worry about glibc version? (As God intended imo; not religious but games should be one contained thing imo) Am curious to see what it does to avoid a static build.

The love2d static build story was a tangent to my 2016 challenge to ship one game every month of the year. The tangent ended up delaying the March game indefinitely, and thus ending the challenge... My memory is a bit hazy, so apologies for the scarce/imprecise details. I really, really wanted to ship binary builds for the three major platforms: Windows, Mac, and Linux; so that my friends and strangers could actually…

Would putting together a Linux Appimage work or one of those other 'bundles' like flatpak?

Re: BSD on Windows: Things I wish I knew existed

#114

Post by Projectiboga » Tue, Dec 12, 2023, 4:35 PM UTC

partomniscient wrote: post #32

doublerabbit wrote: post #5

Earlier quoted context omitted.

This is where we should be, native support of Linux on Windows and native support of Windows on Linux. Executables should be cross-compatible, we somehow ended up in a reality of monopolistic -- 1v1. I would enjoy it to break free at some point but I doubt it. Just about everything now is it's own garden with a tiny API gate to allow you access to the minor features of the whole collection. I am aware of WSL and the…

But they should all break on MacOS and refuse to be cross-compiled for Windows/Linux? I agree with your idealism, but I think the best we're going to get is more or less what we have now, otherwise we end up in the space where program x works with o/s y version z subsystem q, but not the other combinations you'd hope for. I'm still annoyed that we don't design enough for the future that when a new O/S version/archite…

Extra annoying as Apple's ability to share a printer was so cool. I'm holding our TV Mac Mini to Mojave to keep compatibility w an older and an even older scanner. Oh and Turbo Tax went backward after only being the new version of Mac OS they went back to Mojave and two previous versions that they will run under.

Re: BSD on Windows: Things I wish I knew existed

#115

Post by milutinovici » Wed, Dec 13, 2023, 9:15 AM UTC

temac wrote: post #106

krylon wrote: post #77

Earlier quoted context omitted.

The kernel, I've been told by people more knowledgeable about this things than myself, is a work of beauty. But the layers and layers of Win32 that sit on top of it do a great job of covering that up.

I fail to see what is particularly brillant about this kernel. Drivers are convoluted. IRQL is convoluted. The supposed distniction between "kernel" and executive has little definition and is convoluted (esp given it duplicates somes primitives for no real reasons). The HAL was a false good idea and Cultler himself agree with that. The network stack splitted betwen user and kernel space makes no sense (and the story…

Which kernels are good?