This way, one package covers multiple Puppies.įor 0 AD, AFAIK it's always been available through the repos. Having combined both in this fashion, I then used the same trick I employ in some of the 'portable' browser launchers, and grepped /etc/os-release to auto-detect the Puppy in use.then wrote the main launch script to fire-up the appropriate shell-script accordingly, depending upon the required version of libcurl. The shell scripts auto-detect architecture and select the appropriate binary. So I put the libcurl4-compatible binaries in a sub-directory within the 'bin_unix' directory of the libcurl3-compatible build, duplicated & re-named the assaultcube.sh 'launcher' & modified it to point at that. The only part that varied was the actual binaries, which are only a few MB in size. I was contemplating building two different packages, but then I realised that the bulk of each package was simply data.and identical across both packages at that. I found the older libcurl ran OK with Tahr & Xenial, whereas the newer libcurl played nice with Bionic & Fossa. And then there's my 'daily-driver', a 'spin' on BK's old Quirky64 'April' 7.0.1, which runs some stuff natively, and some from a Fossapup64 'chroot'. plus a couple of older 32-bit 5-series Slackos, and a copy of 10wt3ch's Studio 1337, frankly one of the most complete & amazing Puppy-based DAWs I've ever found. When I found out about the different libcurl versions I thought I'd better download both to try them out. I quite enjoy the odd half-hour or so with these sorts of things, though luckily I DO know when to quit.!! However, I've always liked FPS games ever since a mate introduced me to Doom & Quake back in the mid-90s. Frankly, I can think of better things to do with my time, but as a full-time carer, I get days when it's all go from dawn till dusk, then other days when I have a ton of spare time to myself. I'll state here and now, I am NOT a hard-core "gamer". When you mentioned there was a Linux port, I thought "Hmmm." and the cogs started creaking and groaning as the rust was forced off them! AssaultCube is summat I've been fooling around with for years, but I've always used the Windows-portable version under WINE. I didn't exactly see your mention in the other thread as a "request". The usual Menu entry can be added if required, as mentioned above. Place it anywhere you want, though outside the 'save' IS preferable If anyone should fancy giving this a look, y'all can find it here:. and who am I to deny the pleasures of this neat FPS to the Puppy membership, just because they don't all run the very newest of everything all the time? This way, just about everybody can enjoy it.! v1.3, however, because it's been compiled against very new versions of everything will ONLY run under Fossapup64 or newer. The upshot is this v1.2 will run with a boatload of Puppies across the spectrum. I know this sounds horrendously out-of-date, but there was a huge gap between the two builds, due to the developer having a ton of personal issues over an extended period of time. This is the previous v1.2 build, which is approximately 7 years old. The usual scripts permit the addition of a Menu entry to run it from wherever the portable is located.įor those of you interested in such stuff, this is NOT the very latest v1.3 build. I've surprised myself with this it all seems to work rather nicely! The portable's main LAUNCH script auto-detects which version of Puppy is in use, and selects the appropriate launch shell script to use, along with performing the usual sym-link gymnastics with the config files. Given that the bulk of the app is simply data - the actual binaries are pretty small - I've combined the two sets of binaries together with two distinct launchers (which auto-detect your OS architecture & fire-up the appropriate binary for you). The build compiled for libcurl3 runs a treat under Tahrpup/Xenialpup, while that compiled to work with libcurl4 runs nicely under Bionicpup/Fossapup. I very soon discovered there's several different builds, largely dependent on the version of libcurl that's installed. That's compared to many others being easily several gigabytes in size, so this is a "featherweight" by comparison. It's quite svelte by gaming standards the entire package, as built, is only around 70 MB. For me, it's just a side benefit, because I have WINE installed for many other things.but I wouldn't expect anyone to install WINE just for this. I've been fooling around with it for years via the Windows portable app running under WINE. With many thanks to, I'm now aware that the classic FPS game "AssaultCube" actually has a Linux port.
0 Comments
Leave a Reply. |