PiCore and Omxplayer

[jodel]

How should I go about trying to get Omxplayer running on PiCore?
Jodel

[bmarkus]

How should I go about trying to get Omxplayer running on PiCore?
Jodel

You must install it from source.

[jodel]

Thanks.  Has anyone tried to do this and how did it go?

[onelife]

Heyo all,

Does anyone know if this did eventually work? OMX form source that is?

I'm looking for a way of playing "video" and displaying images with PiCore but from command line and also ideally keeping CPU down and / or taking advantage of the GPU.

BIG Thanks

[bmarkus]

omxplayer from Raspbian works fine in piCore 5.3.1, it can play fullscreen vide with audio in sync. Havn't checked all features but in general it is ok. If you are interested I can make a short guide how to install it.

[dae87]

Hi,
I would like to know how to build omxplayer from source.

Thanks.

[bmarkus]

Hi,
I would like to know how to build omxplayer from source.

Thanks.

See upstream forum, web, git, etc.

[sixgunz]

omxplayer from Raspbian works fine in piCore 5.3.1, it can play fullscreen vide with audio in sync. Havn't checked all features but in general it is ok. If you are interested I can make a short guide how to install it.

Hi Béla

I would be very interested in the guide for how to install.

Thanks,

Glenn.

[paperone]

I apologize to revive an old thread but I just would like to know whether there exist any guide on how to compile omxplayer from source. I cloned the source from https://github.com/popcornmix/omxplayer and tried the build script but it require some packages and dependencies that I do not know how do install since the build script was meant for Debian.

Do you have any guide that I can refer to or any article out there that I can learn from in building from source? Thank you for your time!

[Rich]

Hi paperone
Based on this:

Code: [Select]

REQUIRED_PKGS="ca-certificates git-core subversion binutils libva1 libpcre3-dev libidn11-dev libboost1.50-dev libfreetype6-dev libusb-1.0-0-dev libdbus-1-dev libssl-dev libssh-dev libsmbclient-dev gcc-4.7 g++-4.7 sed pkg-config"
Found here:
https://github.com/popcornmix/omxplayer/blob/master/prepare-native-raspbian.sh
My best guess based on what I see in the current repository is that you need to install:

Code: [Select]

compile-essentials.tcz
pcre-dev.tcz
libidn-dev.tcz
boost-dev.tcz
freetype-dev.tcz
libusb-dev.tcz
dbus-dev.tcz
openssl-1.0.1-dev.tcz
libssh2-dev.tcz
samba4-dev.tcz
pkg-config.tczI don't know if all the version numbers are suitable for this.
One of the required packages listed is  libva1 , which I don't see listed, so you'll probably have to track it down and
compile that first.
This should help for build instructions:
http://wiki.tinycorelinux.net/wiki:creating_extensions

[paperone]

Thank you for the reply, Rich! I am going to follow along the info you've just posted and try the build instructions.

[Rich]

Hi paperone
I think this might be the missing  libva1  dependency:
http://www.freedesktop.org/wiki/Software/vaapi/#git

[paperone]

Thanks Rich!

Ok, I just went through your info and the wiki on creating extension and also the CoreBook. I understand only certain part and I am still trying to digest and wrap my head around how to compile omxplayer.

I don't know what steps and requirements it entails yet to be able to compile omxplayer so I hope you can bear with me on my question. Here are the questions:
- Reading through your link on http://wiki.tinycorelinux.net/wiki:creating_extensions — to compile omxplayer, does it mean I need to find and download those dependencies or extensions in TC parlance as listed in the omxplayer project build script and then embeded it along in the omxplayer extension that still need to be build?
- I was on piCore 6.0 X on Raspi Model B but I couldn't find the compiletc.tcz extension using the App Browser. Then I tried using TinyCore 6.4.1 under VirtualBox, I was able to find and load compiletc.tcz extension. Does it mean I can only create the extension on TinyCore then pack them up, copy and install the generated omxplayer extension on piCore?

[Rich]

Hi paperone

I was on piCore 6.0 X on Raspi Model B but I couldn't find the compiletc.tcz extension using the App Browser.

It's called  compile-essentials  when you are running on PI.

You need to install the following using the  Apps  utility:

Code: [Select]

compile-essentials.tcz
pcre-dev.tcz
libidn-dev.tcz
boost-dev.tcz
freetype-dev.tcz
libusb-dev.tcz
dbus-dev.tcz
openssl-1.0.1-dev.tcz
libssh2-dev.tcz
samba4-dev.tcz
pkg-config.tcz That should provide most of the tools and dependencies you need to build  omxplayer.

Here's a link for the latest libva tarball.
http://www.linuxfromscratch.org/blfs/view/svn/x/x7driver.html#libva
You'll need to compile that before you can build omxplayer.

[paperone]

Oops. Sorry for my ignorance, while waiting for your reply, I did some reading and test. I need to clarify one thing.

I was reading through https://github.com/puppetlabs/Razor-Microkernel/wiki/Building-your-own-TCL-Extension and tried to follow along but didn't quite manage to get the extension compilation done. Okay, don't rain down at me, lol. The article was created in 2012 so I think it was probably outdated in some way such as a few extensions are no longer available when I tried to install them. Knowing the fact that some stuff is missing, I exported the flags such as described in the wiki, it gave me: "checking whether the C compiler works... no".

Ok, coming back to the idea of an extension — in reading between the few articles, it started to make sense to me. Correct me if I am wong, when building an extension, we're essentially doing a few steps?
- Install the build tools such as compiletc.tcz, squashfs-tools.tcz, etc.
- Find and install all dependencies, these dependencies must be already "converted" to TinyCore extensions. For example, the omxplayer requires the the dependencies as you listed above — some are in tcz format and some others aren't.
- For those that aren't, we need to "convert" them in tcz.
- Finally, find the source file of the new extension eg: omxplayer. Do "configure" with some parameters and build it using "make".
- Move the build package or executable into their own folder and pack it using "mksquashfs".

Is the steps correct?