Slow but steady progress adding to T2

No comments
I was logging progress here:

However, decided to start a new thread.

Some more:


gview home page:

gwhere home page:

Gwhere needed a lot of TLC to compile. Feasible as it is written in C -- if it had been written in C++ it would have been a hopeless case.

...that's because the C++ developers shift the goal posts, unlike C that basically remains the same over the years.

I wonder if anyone uses these apps? I have put gview and gwhere into all my pups, for years and years.
Gwhere is a nice concept, though I never used it myself. It kind of filled a niche, so I always put it in.

The end of Dr Dobb's Journal

No comments
Oh wow, this is the end of an era:

Back in the early 90's I used to purchase Dr Dobb's from my newsagent. I even contributed a couple of articles:

Object oriented flow design:

TERSE operating system:

Do you old-timers remember Byte magazine? In its heyday it was about half an inch thick. Another one that I used to buy sometimes.
Byte magazine bit the dust many years ago.

Gpptp v2.0 in T2

No comments
I announced recently the work that Puppy Forum member jafadmin has done, developing Gpptp, which is PPTP VPN client:

The PET package has two binary executables in it. I have taken the sources out to a separate package, named 'gpptp-2.0' and the compiled binary pkg will have the same name.
The PET, without the binaries, is now named 'gpptp-noarch-2.0'.

The latter will be uploaded to the Quirky noarch PET repo soon. It will be here:

The former will be uploaded to the April sources repo soon. That is here, not complete yet:

The binary packages created by T2 will be uploaded here, but there is nothing there yet:

Continuing to import into T2

No comments
I am working intensely on this. Days are rolling past, I will keep going until they are all in.

I am logging progress in this blog thread:

pup-tools in T2

No comments
I posted about compiling BaCon in T2:

That allowed the next step, which is to compile all of my utilities written in BaCon.

In woofQ I have centralised all compilable sources, that are inside woofQ. These are inside a directory named 'source', and there is a script that will construct a source tarball for T2, named pup-tools-<date>.tar.gz.

This script also asks for logos and name of the distro. So, for the example of 'welcome1stboot', the first-boot welcome window, which is actually welcome1stboot.bac, written in BaCon, this is now customisable.
In Quirky, welcome1stboot displays the Quirky logo and text like this:

" Welcome, this is the first time that you have started Quirky"

The logo can be changed to whatever you want, and the name "Quirky" replaced with whatever you want.

So, the generated source tarball can be supplied to T2, and T2 will generate a binary package, with the same name, pup-tools-<date>.tar.bz2.

'pup-tools' needs to be in the package-list of your target-build in woof. Here is the current content of the binary pkg:


Most of these are written in BaCon. Only vercmp, getcurpos and printcols are written in C. I compiled vercmp and printcols statically with dielibc.

Pages: [1] [2] [3] [4] [5] ...