Digital clocks gluqlo, fliqlo for Linux as "portable ROX Application Directory"

[HerrBert]

Not sure if this is the right place to post, since Nixie Clock appears in Utilities... (feel free to move)

I'm not that much experienced in coding, but i've tried to compile gluqlo: fliqlo for Linux.
Works as is, but i was unhappy with it's filestructure and colors. So i changed colors and tried to make it kind of "portable" and ended up with a ROX Application Directory.
Compiled in Slacko 6.3.2 (32bit).

gluqlo-1.1_roxapp_x86.tar.gz

(53.98 KiB) Downloaded 54 times

Since we don't have a working xscreensaver in Puppy, you have to start it manually or by xautolock (if installed).

Unpack to a Linux ext-formatted partition, right-click and choose Help for (little) more Information...

[rockedge]

Hello HerrBert,

Nice!
For me to get it to work on a Bionic64-CE (woof-CE made) I had to download and install this -> https://packages.ubuntu.com/bionic/i386 ... 0/download
and then in a terminal:

Code: Select all

ldconfig

I like it a lot thank you.

[taersh]

For me to get it to work on a Bionic64-CE (woof-CE made) I had to download and install this -> https://packages.ubuntu.com/bionic/i386 ... 0/download
and then in a terminal:

Code: Select all

ldconfig

How do you run a 32bit binary in 64bit Puppy?
I needed to compile this by myself to have it working in 64bit Puppy.

Though, nice one! Works also in full screen mode when having two monitors.

[mikewalsh]

@ rockedge:-

Perhaps this one might work better?

https://www.omgubuntu.co.uk/2016/11/glu ... ver-ubuntu

Down the bottom, you can access the .deb package built for Ubuntu 16.04 LTS.....i686 or amd64. Worth a try, perhaps? I daresay both packages would be worth experimenting with; this one and Herr Bert's.

How do you run a 32bit binary in 64bit Puppy?

Usually with the 32-bit_compat_libs.sfs, where one's available, Rainer. Though see if the above-mentioned Xenial64 .deb works as a starting point for you.....


Mike.

[taersh]

Thanks.

Yes, I have a 32-bit compatibility .sfs.
It is named compat32_ArtStudio64_1.0.0.sfs, but I don't use it.
Had compiled gluqlo for my OS and works fine.

[mikewalsh]

Thanks.

Yes, I have a 32-bit compatibility .sfs.
It is named compat32_ArtStudio64_1.0.0.sfs, but I don't use it.
Had compiled gluqlo for my OS and works fine.

Mike.

[rockedge]

Gluglo-1.1.1 built in Fossapup64-9.0.5 now as a SFS and also supplied in DOTPET form

gluglo-600px.jpg (29.84 KiB) Viewed 816 times

gluqlo-1.1.1-x86_64_9.0.5.sfs

(60 KiB) Downloaded 50 times

gluqlo-1.1.1-x86_64.pet

(58.91 KiB) Downloaded 49 times

[bigpup]

Thanks.

Yes, I have a 32-bit compatibility .sfs.
It is named compat32_ArtStudio64_1.0.0.sfs, but I don't use it.
Had compiled gluqlo for my OS and works fine.

The 32bit compatibility sfs loaded has to be the one specifically made for the 64bit Puppy version being used.
They all should have a specific one available.

If not listed in the post about the specific Puppy version.
They can be found here for official Puppy versions.
http://distro.ibiblio.org/puppylinux/
Usually found in the specific Puppy version pet_packages directory.

[taersh]

Thanks.

Yes, I have a 32-bit compatibility .sfs.
It is named compat32_ArtStudio64_1.0.0.sfs, but I don't use it.
Had compiled gluqlo for my OS and works fine.

The 32bit compatibility sfs loaded has to be the one specifically made for the 64bit Puppy version being used.
They all should have a specific one available.

If not listed in the post about the specific Puppy version.
They can be found here for official Puppy versions.
http://distro.ibiblio.org/puppylinux/
Usually found in the specific Puppy version pet_packages directory.

Yes, I know this. My Puppy is a Woof-CE build made from Bionic64. Its base .sfs is named nempup_ArtStudio64_1.0.0.sfs - since it is a N.E.M.E.S.I.S. Puppy. And I named my 32-bit compatibility sfs just following the rules for names like e.g. adrv_bionic64_8.0.sfs. So, in my case it's named compat32_ArtStudio64_1.0.0.sfs. To me it's simply not logical to exclude the 32-bit sfs from naming rules of the .sfs modules related to a Puppy.

The 32-bit compatibility sfs of my ArtStudio64 is listed inside of /etc/DISTRO_SPECS and my ArtStudio64 has additional boot options to boot it with or without these extra sfs modules. E.g. padrv=on will load all the extra .sfs modules, but padrv=off will not load them. Loading extra sfs is on by default. And similar it goes for the 32-bit compatibility sfs. E.g. pcompatsfs=on will load it. Loading the 32-bit compatibility sfs is off by default.

This way I can boot my ArtStudio64 in different setup without to move extra sfs or 32-bit compatibility out of the way into a sub-directory or another partition. This is really smart, as it avoids remastering with extra sfs etc. included into the remastered base sfs. N.E.M.E.S.I.S. ArtStudio64, the smartest Puppy on the forum!