Skip to content

Commit

Permalink
Links fixed
Browse files Browse the repository at this point in the history
  • Loading branch information
@bkauler
bkauler committed Oct 30, 2017
1 parent fe8329a commit 3f2f8a3
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion readme.htm
View file
Expand Up @@ -103,7 +103,7 @@ <h2> Getting started</h2>
OK, now to using it...<br>
<pre># cd oe-qky-src<br># ./create-oe-qky</pre>Up-one level, you will see newly-created folders "downloads" and "oe-quirky". Folder "oe-quirky" has everything, and you can get setup to do a build:<br><pre># cd ../oe-quirky<br># source oe-init-build-env buildPC</pre>Folder "buildPC" is building for a PC, x86_64 CPU. Alternatives are "buildPC32" for a PC with i686 32-bit CPU, and "buildPi" is for a Raspberry Pi2 and Pi3.<br><br>A quick sanity test is to check that the layers are found:<br><pre># bitbake-layers show-layers</pre>To do the actual build, you must have an Internet connection, a reasonably fast one -- if using wi-fi provided by a telco, 4G is strongly recommended over 3G.<br>Also, a fast PC with plenty of RAM is required. Although OE state a minimum of 2GB RAM with swap partition, at least 4GB is recommended.<br><br>Note that the Internet connection must be maintained throughout the build, as some packages, such as libreoffice, download extra source packages during compile.<br>In otherwords, you cannot download all source packages prior to commencing the build.<br><br>An annoyance is that libreoffice does not preserve the downloads globally for other builds. So, everytime that libreoffice gets compiled, it has to download lots of extra packages.<br><br>Off we go, for the next few hours (or days, depending on your PC):<br><pre># bitbake core-image-quirky</pre>Barry's main PC for doing OE builds has a i5-4200 3.10GHz CPU, 16GB RAM and 1TB hard drive, and a build takes about 9 hours.<br><br>Before or after the build, you can run this command to obtain lists of all chosen packages and their dependencies:<br><pre># bitbake -g core-image-quirky</pre>...you will then see files "pn-buildlist", "task-depends.dot" and "recipe-depends.dot" in the "buildPC" folder.<br><br>If you intend to export the packages to woofQ, the Quirky Linux build system, the above command is essential, as the files it produces are read by the packages-import script in woofQ.<br><br>At the end of the build in OE, you will see many warning messages about incorrect packaging. These do not matter, as the export to woofQ does not use the OE packaging stage -- instead, the 'image' folder in each package build (which has the result of 'do_install') is read by woofQ and woofQ does its own packaging.<br><br>Also, if for any reason the final step, 'do_rootfs', fails in OE, that does not matter, as woofQ builds its own rootfs.<br><br><h2>Deploy</h2>coming soon<br><br><h2>About Quirky Linux</h2>Quirky and Easy, originally forks of Puppy Linux, inherit the very small size yet with just about every package that you will need, as well as simplicity and power-to-the-user.<br><br>To achieve the small size, careful choices are made of which packages and dependencies to use. It is useful to note what is <i>not</i> in Quirky:<br><br><blockquote><font color="#ff0000">avahi esound gtk+3 </font><font color="#ff0000"><font color="#ff0000">jack </font>multilib </font><font color="#ff0000"><font color="#ff0000">pulseaudio </font>qt systemd</font> <br></blockquote><br>...at least, these exclusions are for the build in OE. Some puppies have gtk+3 and qt. They may also inherit multilib and dependencies of whatever distribution is used as the source of binary packages. But <i>none</i> of them have pulseaudio or systemd! (Puppy manages to castrate these if binary packages depend on them).<br><br>Future builds in OE may include gtk+3 or qt apps, however for now all gui apps in Quirky are gtk+2 or x11 based. Note, there are various reasons for not using gtk+3.<br><br>Many major applications, such as Firefox, SeaMonkey and LibreOffice, build with gtk+2. In some cases, for example Evince, where gtk+2 has been abandoned, an older version is used, with patches to keep it "up to date".<br><br>Another important factor is that there is a very prolific Puppy developer community, and there are hundreds of GUI applications specifically created for Puppy, most of them using gtk+2.<br>Thus, we have no difficulty with populating a distro with an extensive suite of GUI utilities and applications with only gtk+2 and x11 available.<br>
<br>
About Quirky itself, what is it?<br>Quirky Linux was forked from Puppy Linux when Barry retired from maintaining the latter. Quirky is Barry's plaything, to experiment with new ideas. Consequently, there have been major architectural changes with different releases of Quirky. The recent offshoot Easy Linux, is another experimental architecture.<br><br><br><h2>Links</h2>Puppy related:<br><ul><li>Woof-CE: <a href="http://murga-linux.com/puppy/viewtopic.php?t=101174">http://murga-linux.com/puppy/viewtopic.php?t=101174</a> <br></li><li>Forum: <a href="http://murga-linux.com/puppy/">http://murga-linux.com/puppy/</a>&nbsp;&nbsp; <br></li><li>Home site: <a href="http://puppylinux.com/">http://puppylinux.com/</a>&nbsp;&nbsp;&nbsp; <br></li></ul>Quirky related:<br><ul><li>Quirky x86_64 8.1.6: <a href="http://barryk.org/news/?viewDetailed=00496">http://barryk.org/news/?viewDetailed=00496</a>&nbsp;&nbsp; <br></li><li>Easy: <a href="http://barryk.org/easy/how-easy-works.htm">http://barryk.org/easy/how-easy-works.htm</a>&nbsp;&nbsp; <br></li><li><br></li></ul>To find out more about what Barry is doing, read his blog:<br><a href="http://barryk.org/news">http://barryk.org/news</a> <br>
About Quirky itself, what is it?<br>Quirky Linux was forked from Puppy Linux when Barry retired from maintaining the latter. Quirky is Barry's plaything, to experiment with new ideas. Consequently, there have been major architectural changes with different releases of Quirky. The recent offshoot Easy Linux, is another experimental architecture.<br><br><br><h2>Links</h2>Puppy related:<br><ul><li>Woof-CE: <a href="http://murga-linux.com/puppy/viewtopic.php?t=101174">http://murga-linux.com/puppy/viewtopic.php?t=101174</a> <br></li><li>Forum: <a href="http://murga-linux.com/puppy/">http://murga-linux.com/puppy/</a>&nbsp;&nbsp; <br></li><li>Home site: <a href="http://puppylinux.com/">http://puppylinux.com/</a>&nbsp;&nbsp;&nbsp; <br></li></ul>Quirky related:<br><ul><li>Quirky x86_64 8.1.6: <a href="http://bkhome.org/news/201701/quirky-816-x8664-released.html">http://bkhome.org/news/201701/quirky-816-x8664-released.html</a>&nbsp;&nbsp; <br></li><li>Easy: <a href="http://bkhome.org/easy/">http://bkhome.org/easy/</a>&nbsp;&nbsp; <br></li><li><br></li></ul>To find out more about what Barry is doing, read his blog:<br><a href="http://bkhome.org/news">http://bkhome.org/news</a> <br>
<br>
</td>
</tr>
Expand Down
6 changes: 3 additions & 3 deletions readme.md
View file
Expand Up @@ -144,12 +144,12 @@ Puppy related:

Quirky related:

* Quirky x86_64 8.1.6: [http://barryk.org/news/?viewDetailed=00496](http://barryk.org/news/?viewDetailed=00496)
* Quirky x86_64 8.1.6: [http://bkhome.org/news/201701/quirky-816-x8664-released.html](http://bkhome.org/news/201701/quirky-816-x8664-released.html)

* Easy: [http://barryk.org/easy/how-easy-works.htm](http://barryk.org/easy/how-easy-works.htm)
* Easy: [http://bkhome.org/easy/](http://bkhome.org/easy/)

To find out more about what Barry is doing, read his blog:
[http://barryk.org/news](http://barryk.org/news)
[http://bkhome.org/news](http://bkhome.org/news)

</td>

Expand Down

0 comments on commit 3f2f8a3

Please sign in to comment.