site  contact  subhomenews

gtk1 and gdk-pixbuf0 compiled in OE

December 13, 2018 — BarryK

glib1 (glib version 1.2.10) got compiled in OpenEmbedded yesterday:

Have now succeeded with gtk+ 1.2.10 and gdk-pixbuf 0.22.0, see the oe-qky-src repository:

In the next release of Easy, will be able to run gtk+ 1.x applications, if desired. I have in mind one that I want to play with... 

Tags: oe

glib 1.2.10 compiled in OpenEmbedded

December 12, 2018 — BarryK

Compiled in 'oe-qky-src' that is, my fork of OpenEmbedded. I have an aim to be able to compile and run gtk+ 1.2.10 applications in EasyOS. For that, it is necessary to compile glib 1.2.10, gtk+ 1.2.10 and gdk-pixbuf 0.22.0.

These are ancient packages, released back around 2001 - 2002. Not surprisingly, there are some issues when compiling them now. I found some patches, from Arch Linux and the T2-project, and was able to compile in a x86_64 host system. Cross-compiling in OE, though, is a challenge.

So far have only done glib. There are some very old patches for compiling glib 1.2.10 in the archived "classical" OE, which were helpful.

It was a struggle, took several hours today, but finally worked:

Fixing the old autotools, etc., was achieved by hacks. 'ltconfig' insisted that it could not create shared libs, was able to override.

Next up, gtk+ 1.2.10 ... 

Tags: oe

Ghostscript compiled with libgs in OE

December 02, 2018 — BarryK

The official OpenEmbedded/Yocto project compiles the ghostscript package with a big monolithic 'gs' binary. However, there are some packages that want 'libgs' as a dependency. So, the recipe in OE needs to be modified to generate a small 'gs' with shared 'libgs'.

Fortunately, Andrew has figured out the required changes to the recipe:

I used that as a basis, and my recipe is here:

And a modification to fix compile fail:

There was a package that I wanted to compile recently, that had libgs as a dependency, which prompted this revisit to OE. 

Tags: oe

Patch for ROX-Filer fix possible slow running

November 04, 2018 — BarryK

Puppy Forum member jamesbond posted a patch that fixes a potential slow-down of ROX-Filer:

That was posted in 2016! I have only just seen it. This is the thing with the Puppy Forum, so much going on, so many great things happening, it is very easy to miss stuff.

You will see in the above link, some testers had difficulty applying the patch. That's because there is different source and they were patching a later fork of ROX-Filer. My source is the original from 2011, with various patches applied.

For EasyOS, ROX-Filer is compiled in 'oe-qky-src', and I have now applied jamesbond's patch:

Thanks James!

Tags: oe

android-tools and adbfs-rootless in OE

August 08, 2018 — BarryK

I want to incorporate simple automatic-discovery file transfer to and from my phones into EasyShare. So far, have investigated 'adbfs-rootless', which is a fuse filesystem for adb:

'adb' is a utility from Google, a kind of communication bridge between a PC and Android phone. I have used this utility many time before, for example:

It would be good to have the 'adb' and 'fastboot' utilities in every future EasyOS and Quirky, so 'android-tools' in OpenEmbedded is now in the package build-list:

Then created a new recipe for 'adbfs' (actually 'adbfs-rootless') and added that to the package build-list:

The instructions to use adbfs are only given for usb-connection. Basically, usb-debugging has to be turned on in the phone, no special app required. In EasyOS, it was very simple:

# mkdir /mnt/phone
# adbfs /mnt/phone

...navigate ROX-Filer to /mnt/phone, and there is my phone, everything available. Some areas are unavailable, due to the phone not being rooted, however, I can access all my files in /mnt/phone/sdcard.

This is good, definitely a contender to be integrated into EasyShare!

Tags: oe

Fix widget order for gtkdialog, aarch64

July 27, 2018 — BarryK

Gtkdialog is used extensively in Puppy Linux and derivatives, for GUI frontends to shell scripts. It is a great tool, with many contributors over the years -- the "greatest" of these would be Puppy Forum member thunor, who undertook to greatly enhance gtkdialog after the project was abandoned by the original developer. Thunor moved on, and the project is now hosted on github, with other contributors:

Way back in 2012, when we were playing with the puppies on the Raspberry Pi, we discovered that gtkdialog rendered the widgets in reverse order in a window, so, for example, the "OK" button would be at the top of the window instead of the bottom. Puppy Forum member jamesbond (one of the key developers of Fatdog), provided a patch, that thunor applied to version 0.8.2.

Fast forward to now, I found that bug has returned for aarch64. I consulted with jamesbond, and have a patch, which is in my OE repository:

It tests if the "__aarch64__" gcc preprocessor macro is set. When I first tested this, it seemed that it was not set, so I found this way to list all of the gcc preprocessor macros:

# gcc -x c /dev/null -dM -E

...yep, "__aarch64__" is set to "1" on my Pi3. Note, I googled around, and someone else tested for "__ARM_ARCH_ISA_A64" -- that works too. 

Tags: oe

meta-qt5 layer now in oe-qky-src

July 15, 2018 — BarryK

A little over a week ago, I added the meta-qt5 layer to oe-qky-src, my fork of OpenEmbedded. However, it broke the build of some packages.

So, I went on a journey, exploring how to compile Qt5 without the meta-qt5 layer, from basic principles. A very intense several days, ended with frustration. Well, lots of frustration during those several days!

I did get it to build, using autotools only, but only for x86_64 host and x86_64 target. Kept getting errors when attempted cross-compile for aarch64 target.

Yesterday, gave up, and went back to the meta-qt5 layer, this time hunted down why it's introduction caused some other packages to fail.

Got it sorted, qt5 5.10.1 now builds, but have not yet ported any qt5-based apps into oe-qky-src. Did attempt Scribus, but got a compile error. For now, will build Scribus in the final running system.

This morning, tried to use Smartgit to commit the latest changes. Did something wrong... it seems, when committed a couple of files and a directory together, Smartgit got confused. Smartgit seems to be thinking that the 'meta-qt5' folder is a file!

Git is very powerful, but when something goes wrong, you can really get your knickers in a twist.

To get it uploaded, here it is as a tarball:

Expand somewhere, it will expand to folder 'oe-qky-src', and there is a readme inside.

Right, now to fix Smartgit...

OK, fixed. The problem was, folder meta-qt5 had a .git folder in it, which confused Smartgit. See commits for July 15, 2018:

EDIT 20180717:
I built EasyOS in woofQ from binary packages imported from oe-qky-src, then attempted to compile Scribus. Lots of configure errors. I found that .cmake files in /usr/lib/cmake are somewhat broken. They are setup to work inside OE. I have fixed them, the fixes are in the template files in woofQ, woof-code/packages-templates/qtbase, qttools, etc.

Interesting observation: cmake seems a lot more troublesome in a cross-compiling environment than autotools-based projects. This is an interesting observation due to the praise for cmake that I read everywhere, and some projects, such as Scribus going over to it.

Tags: oe