You could have a look at the GIS Internals stable releases. They provide precompiled binaries for windows with a broad range of dependencies (including almost all those I listed in my previous post). If the GIS Internals paths can be found by the various gdal-stack aliens then they will run system installs.

Edit: Be sure to also get the download flagged as "compiled libraries and headers"

Another edit: I just tested with the GIS Internals files and the alienfile probe for geos does not work (the probe currently uses geos-config, which is not included).

Rather than try and get things to work on the inferior OS you might find it worth the effort (to say nothing of being less headaches) to install a docker host and see if you can't get a dedicated environment running a decent real OS instead. With that available then you could install the more off-the-shelf tool chain into it more easily (theoretically . . .). Instead of trying to jump through all these hoops getting this (as you say elsewhere in the thread) occasional procedure running "native" you can just spin up a container to process the results and dump the output out as you need it into a shared volume that you then work with from your "normal" platform.

Edit: Looks like there's an osgeo/gdal available which you probably could build upon.

As I've reached the point I've got to, my gut feeling is that it is worth continuing. Perhaps not for this project, but certainly for what I am learning in the process of doing this. Previously, the only use I've made of unpack is to split up an authentication string.

I think knowing more about pack and unpack would be beneficial to me. Thanks to soonix and Marshall my understanding of these two functions in improving. That alone makes continuing worthwhile.

Certainly a good learning opportunity and from the (cursory) read over the linked docs it looks like those should well serve. Having something “tangible” to use for practical samples is great; I’d just rather (for $work purposes) defer to off the shelf and play with things on the back burner.

The cake is a lie.
The cake is a lie.
The cake is a lie.

I still would like binary dump as I request in here.

I don't want to get into the idea of "real" vs "fake" OS. Windows is certainly "real". I've worked with several variants of MS O/S's and several variants of Unix, one IBM mainframe OS and several real time O/S's. They are all "real" and have their own jobs.

Your question is interesting and a little bit different than what I normally deal with. Worst case, I believe that I can write an inline C subroutine that will do what you want (as long as we are both on 64 bit little endian architecture). Although I don't think that is necessary.