oe-qky-src on github

'oe-qky-src' is my custom layer for OpenEmbedded, to compile from source all the packages required for a typical Quirky, Puppy, or other Puppy-derivative.

Furthermore, it is now on github:
https://github.com/bkauler/oe-qky-src

There is a nice "readme".

If you look in quirky/meta-quirky/recipes-quirky, there are about 140 recipes, packages that I have imported to OE.
The reason that I had to do all this work, is partly because OE targets embedded systems rather than a generic Linux distribution. Also partly because Puppy and derivatives are different from other Linuxes, with a different selection of packages, and many unique to Puppy.

You will also see folder 'downloads-oe'. This has snapshot tarballs of OpenEmbedded, taken just when the Pyro release was announced. I have provided the snapshots so that anyone building oe-quirky will get the exact same result as me.

To help me manage the github site, I have brought back SmartGit. This is a very nice GUI git manager tool, that I experimented with about a year ago:
http://murga-linux.com/puppy/viewtopic.php?t=106704

...seem to recall, forum member 'gcmartin' put those instructions together into a single file.

Here is my original blog post about SmartGit, April 2016:
http://bkhome.org/news/201604/smartgit-gui-for-git.html

I have got SmartGit installed on my mid-tower desktop PC, as well as the Adobe JRE version 8u131.

I did briefly look at some others, for example Gitkraken, Git-tool and GitAhead, but each one had problems.
SmartGit is very sophisticated, and above all "just works". It is free for non-commercial use.

If anyone downloads 'oe-qky-src' and does a build, they will have binary packages, but then what? They will need woofQ to build a distro. Currently I am only providing woofQ as tarballs, and will upload the latest soon. However, maybe should put that on github also (?).
The woof-CE guys could also import the packages from oe-qky-src, they will need my script '0pre-oe', that will be in the next upload of woofQ.

SmartGit website:
http://www.syntevo.com/smartgit/

---

Comments

I completed the x86_64 'buildPC' build before uploading oe-qky-src to github.

Now I am compiling the x86 32-bit 'buildPC32' build.
I changed the "-march=i586" to "-march=i686", raising the bar a bit. The online gcc documentation does not define exactly what the difference is, only vague statements.
I think that i686 also implies 'mmx' and 'sse' instructions, otherwise a very generic x86 instruction set, which should, I think, work from a PentiumPro and later.

Have hit one fail, 'isomaster' did not compile. So have taken that one out, will compile it in the target distro.

Note, the Yocto 'genericx86' machine target uses "-march=core2", with "-m32". However, after a bit of reading, core2 may have one or two instructions that are not in earlier CPUs.

The same situation with the 64-bit build. Yocto has 'genericx86-64', which I used as the template for my x86_64 build in oe-quirky. It has "-march=core2 -m64" however, this may have one or two instructions that are not in earlier 64-bit pentium CPUs.

I wasn't happy with their choice of core2 as the baseline, but went with it for the 64-bit build, as being new to OE/Yocto was unsure how to change it, that is, to lower the bar a bit.

http://murga-linux.com/puppy/viewtopic.php?t=110453

That's a good place if anyone wants to provide more feedback.

Have imported freememapplet-tray:
https://github.com/bkauler/oe-qky-src/commit/105038473f1ccbd9dde587327d95f600523ab259

Have imported network-tray:
https://github.com/bkauler/oe-qky-src/commit/e82f100e6b8b4876979705b8ad7187b1ae49a57b

Yesterday I did a build for the RPi, fixed a few packages, and it went right through.

Commits can be seen here:
https://github.com/bkauler/oe-qky-src/commits/master

Tags: oe