Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 21 Jul 2017, 10:58
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
OpenEmbedded: compile Puppy from source
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [22 Posts]   Goto page: 1, 2 Next
Author Message
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Wed 10 May 2017, 22:27    Post subject:  OpenEmbedded: compile Puppy from source
Subject description: Use with woof-CE or any other Woof*
 

This is so interesting, and I am having fun. Posting to my blog, which does not allow reader-comments (I disabled that awhile-back due to security problems). So I thought would create a forum thread and invite feedback.

Woof-CE, or any of the earlier Woofs, or my fork woofQ, can build a Puppy or puppy-like distro from binary packages.
Usually, we get those binary packages from another distro repository, such as Ubuntu, Debian or Slackware.

Some earlier pups, for example Wary and Racy, used binary packages that were compiled from source in T2 (see http://t2-project.org/), however, T2 is not maintained, only one guy does some work on it.

An alternative is OpenEmbedded, which the Yocto project uses. This has 75+ active developers. Despite mainly used for embedded devices, OE can compile anything, even LibreOffice.
So, OE could be used to compile the packages for Woof*, even the Linux kernel.

I have done this, and built a first pre-alpha Quirky Linux, using my woofQ. Yep, have compiled almost everything, including kernel, libreoffice, gimp, kodi, firefox.

What I could do, is upload the binary packages somewhere, and they can then be used by any other Woof*

Here is discussion on woof-CE:
http://murga-linux.com/puppy/viewtopic.php?t=101174
http://murga-linux.com/puppy/viewtopic.php?t=96723

01micko has setup woof-CE to compile source packages. As I understand it, it is not a cross-compiler, and is only at beginner stages.
OE runs on a x86_64 host system and can build for any target, such as x86_64, i686 or armv7.

Also, OE could totally replace Woof*, but that is very much down the track.

Anyway, starting this thread, will post here as it progresses, also on my blog. Here is the blog post reporting on "Pyro64" 0.1:
http://barryk.org/news/?viewDetailed=00537

Earlier blog posts:
http://barryk.org/news/?viewDetailed=00535
http://barryk.org/news/?viewDetailed=00534
http://barryk.org/news/?viewDetailed=00531
http://barryk.org/news/?viewDetailed=00529
http://barryk.org/news/?viewDetailed=00530

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Thu 11 May 2017, 11:24    Post subject:  

A bit of a timeline. "Pyro" is the name of the next release of OpenEmbedded, due out this month.

When Pyro is released, I plan to take a snapshot of OE from github, and use that as the basis for my own Quirky Pyro64.

I plan to build a alpha release of Quirky Pyro64, for anyone who wants to play with it.

Also, I plan to upload a tarball of OpenEmbedded with my extensions, so anyone can download it, then just run a couple of simple commands, and it will take off, downloading and compiling everything, from kernel to libreoffice.

What someone could do, is experiment with adding more packages, or change the target build to, say i686.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
sc0ttman


Joined: 16 Sep 2009
Posts: 2405
Location: UK

PostPosted: Thu 11 May 2017, 12:58    Post subject:  

BarryK wrote:
A bit of a timeline. "Pyro" is the name of the next release of OpenEmbedded, due out this month.

When Pyro is released, I plan to take a snapshot of OE from github, and use that as the basis for my own Quirky Pyro64.

I plan to build a alpha release of Quirky Pyro64, for anyone who wants to play with it.

Also, I plan to upload a tarball of OpenEmbedded with my extensions, so anyone can download it, then just run a couple of simple commands, and it will take off, downloading and compiling everything, from kernel to libreoffice.

What someone could do, is experiment with adding more packages, or change the target build to, say i686.

Any chance of getting Alacritty (http://blog.jwilm.io/announcing-alacritty/) or, even better, mlterm-fb working in those Open Embedded builds?


..I've tried and failed numerous times to get mlterm-fb working in any puppy .. not sure why it won't work :/

_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search

Last edited by sc0ttman on Thu 11 May 2017, 13:00; edited 1 time in total
Back to top
View user's profile Send private message 
sc0ttman


Joined: 16 Sep 2009
Posts: 2405
Location: UK

PostPosted: Thu 11 May 2017, 12:58    Post subject:  

..deleted double post..
_________________
Akita Linux, VLC-GTK, Pup Search, Pup File Search
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4719

PostPosted: Thu 11 May 2017, 21:27    Post subject:  

sc0ttman wrote:
BarryK wrote:
A bit of a timeline. "Pyro" is the name of the next release of OpenEmbedded, due out this month.

When Pyro is released, I plan to take a snapshot of OE from github, and use that as the basis for my own Quirky Pyro64.

I plan to build a alpha release of Quirky Pyro64, for anyone who wants to play with it.

Also, I plan to upload a tarball of OpenEmbedded with my extensions, so anyone can download it, then just run a couple of simple commands, and it will take off, downloading and compiling everything, from kernel to libreoffice.

What someone could do, is experiment with adding more packages, or change the target build to, say i686.

Any chance of getting Alacritty (http://blog.jwilm.io/announcing-alacritty/) or, even better, mlterm-fb working in those Open Embedded builds?

..I've tried and failed numerous times to get mlterm-fb working in any puppy .. not sure why it won't work :/
mlterm-fb compiles fine in fatdog64 ... just add --with-gui=fb to the other ./configure options (prefix, libdir,sysconfdir,localstatedir,...) ... although the devs should probably address the cascade of warnings that come up ... it won't build with -Werror set (such as in $CFLAGS) ... then make install mlterm-fb
_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3194
Location: New Zealand

PostPosted: Fri 12 May 2017, 03:33    Post subject: Re: OpenEmbedded: compile Puppy from source
Subject description: Use with woof-CE or any other Woof*
 

BarryK wrote:

Also, OE could totally replace Woof*, but that is very much down the track.


Since it takes a significant investment in time to learn or maintain any build system the well-supported OpenEmbedded system described here seems to me like a very good way forward indeed for Puppy. I realise OE will have a probably steep learning curve, but appears to be a useful system to learn more generally so having it brought to my attention by this thread, I'm certainly excited by the small-system-building possibilities it offers. I'm thus keen to try it out now too.

Thanks for the info.

William

_________________
SomeOfMyWork with links:
dCoreDog
weX, scrox, Precord, Premote, fokSyfEyeR, xhippo-mod, flite_hts_pet
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Fri 12 May 2017, 21:12    Post subject: Re: OpenEmbedded: compile Puppy from source
Subject description: Use with woof-CE or any other Woof*
 

mcewanw wrote:
BarryK wrote:

Also, OE could totally replace Woof*, but that is very much down the track.


Since it takes a significant investment in time to learn or maintain any build system the well-supported OpenEmbedded system described here seems to me like a very good way forward indeed for Puppy. I realise OE will have a probably steep learning curve, but appears to be a useful system to learn more generally so having it brought to my attention by this thread, I'm certainly excited by the small-system-building possibilities it offers. I'm thus keen to try it out now too.

Thanks for the info.

William


Hi, yes, I mentioned that as a theoretical possibility. In OE (and Yocto) you can set it up with a Board Support Layer (BSP) for a specific hardware target, for example Raspberry Pi, and it will gnerate an SD-card image for the Pi .

I don't know if it will happen for the pups though. it is easy enough to import the binary packages from OE into Woof*.

But, to run just one build script, which compiles everything from source and outputs a live-CD or SD-card file -- the thought is enticing!

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1218
Location: the australian mallee

PostPosted: Sat 13 May 2017, 08:29    Post subject:  

BarryK,

You mentioned problems with Kodi on your blog, it wouldn't happen to be version 17.1 would it? Most 'Linux's' are having various problems with this one, maybe it's worth going back a step for your first build.

If you haven't already, have a look at https://forum.kodi.tv the Kodi community forum is always looking for problem entries (and of course solutions) so everyone knows about them.

regards
scsijon

ps nearly got a t2 puppy packageset built without errors finally, then a new ?racy?6 to build in woof for all!
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Sun 14 May 2017, 22:46    Post subject:  

scsijon wrote:
BarryK,

You mentioned problems with Kodi on your blog, it wouldn't happen to be version 17.1 would it? Most 'Linux's' are having various problems with this one, maybe it's worth going back a step for your first build.

If you haven't already, have a look at https://forum.kodi.tv the Kodi community forum is always looking for problem entries (and of course solutions) so everyone knows about them.

regards
scsijon

ps nearly got a t2 puppy packageset built without errors finally, then a new ?racy?6 to build in woof for all!

Yes, it is 17.1.

I have good news, now have text.

/usr/share/gconv folder was missing. Fixed.

Tried kodi, there was a couple of peculiar things. Could go back to 17.0

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
pakt


Joined: 04 Jun 2005
Posts: 1156
Location: Sweden

PostPosted: Mon 15 May 2017, 05:27    Post subject: Regarding NAS  

Barry, I can recommend the Synology DS216J 2-Bay NAS. This is a reliable, fast and quiet NAS.

The DiskStation OS is topnotch, with lots of configuration settings. It even has its own 'app' store!

I use this NAS (in 'RAID 1' aka mirroring) for storage and streaming media. My older DS212j 2-bay unit I bought years ago now serves as an archive.

http://www.austin.net.au/synology-ds216j-2-bay-nas.html

_________________
Puppy unofficial tester (off and on) since v0.9.2
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4719

PostPosted: Mon 15 May 2017, 13:26    Post subject: Re: Regarding NAS  

pakt wrote:
Barry, I can recommend the Synology DS216J 2-Bay NAS. This is a reliable, fast and quiet NAS.

The DiskStation OS is topnotch, with lots of configuration settings. It even has its own 'app' store!

I use this NAS (in 'RAID 1' aka mirroring) for storage and streaming media. My older DS212j 2-bay unit I bought years ago now serves as an archive.

http://www.austin.net.au/synology-ds216j-2-bay-nas.html

Just in case anyone else decides to do this research, I looked into the most economical method of getting a 1Gbit SATA file server and found the banana pi m1 (in headless mode) to be the most bang for the buck (<$40)... plus you get an extra dual core arm system with a mali GPU for distributed builds. Note that later versions of the banana pi use an inferior usb2->sata controller that severely limits speed. Although the product page states that the m1's drive size is limited to 2Tb, various forums report success with 4Tb.

Edit: for usb3 the lemon pi is a similar price point, but it appears to be poorly documented, which in my experience usually means some of the driver work is still incomplete/experimental.

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Mon 15 May 2017, 22:13    Post subject: Re: Regarding NAS  

technosaurus wrote:
pakt wrote:
Barry, I can recommend the Synology DS216J 2-Bay NAS. This is a reliable, fast and quiet NAS.

The DiskStation OS is topnotch, with lots of configuration settings. It even has its own 'app' store!

I use this NAS (in 'RAID 1' aka mirroring) for storage and streaming media. My older DS212j 2-bay unit I bought years ago now serves as an archive.

http://www.austin.net.au/synology-ds216j-2-bay-nas.html

Just in case anyone else decides to do this research, I looked into the most economical method of getting a 1Gbit SATA file server and found the banana pi m1 (in headless mode) to be the most bang for the buck (<$40)... plus you get an extra dual core arm system with a mali GPU for distributed builds. Note that later versions of the banana pi use an inferior usb2->sata controller that severely limits speed. Although the product page states that the m1's drive size is limited to 2Tb, various forums report success with 4Tb.

Edit: for usb3 the lemon pi is a similar price point, but it appears to be poorly documented, which in my experience usually means some of the driver work is still incomplete/experimental.


Yes, I have wondered about a DIY NAS, maybe using one of the specialized Linux/BSD OS's such as FreeNAS.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Mon 15 May 2017, 22:19    Post subject:  

Quoting from my blog:
Quote:
Yes, confirmed that icu 58.2 is causing firefox and seamonkey to be unstable.

So, trying an experiment. Recompiling in OE with icu 56.1, same version as used internally in firefox and seamonkey.

I also added the patches from seamonkeys's internal icu, mindful that it may be one of those patches that fixes the stability problem.


It will be interesting to see how this turns out.

Ubuntu Xenial Xerus 16.04 only has icu 55.x, and I have compiled seamonkey with it, no problem.

Gradually getting there. Hopefully in a few more days, will be able to upload "oe-qky-src", OE with my customization layer, and a Quirky build, codenamed "Pyro64".

I am using Pyro64 every day right now. Just some details need to be sorted out, like SeaMonkey crashing!

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Mon 15 May 2017, 22:30    Post subject:  

The way that OE builds packages is very interesting. Each package is built in isolation.

Unlike other systems such as Buildroot and T2, there is no single target rootfs, that each package gets installed into as it is compiled.

We are familiar with running "configure" and it sees what is installed and makes choices what dependencies to use. OE can't do that, you have to specify all deps in the recipe.

They don't have to be hard-coded deps, there can be conditional tests in the recipe.

It does require more work when creating a recipe, to decide what deps are essential and what are conditional.

This isolation does have advantages. I am seeing this, when doing a rebuild, after having changed icu.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8119
Location: Perth, Western Australia

PostPosted: Fri 19 May 2017, 02:39    Post subject:  

Quirky Pyro64 version 0.2 is uploaded, I have started a new thread:

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

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 2 [22 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0782s ][ Queries: 13 (0.0069s) ][ GZIP on ]