Puppy Linux Discussion Forum

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm ...

These pets were built on my Puppy 4.1 daemon and may need to be installed
together. Provided for your convenience. I do not intend to maintain this
unless I borked something up. Tested over a fresh Puppy 4.1 and seems to
work fine for me.

1. ffmpeg 0.5 stable release
[download]
Description: ffmpeg 0.5 "Bike Shed" March 3, 2009 official release.
If you install this pet and uses xine-lib shared apps, you will have
to update xine-lib or some codecs will not work properly, ex: avc1.

configure notes:
--prefix=/usr --disable-debug --enable-shared --enable-gpl
--enable-libmp3lame --enable-libvorbis --enable-pthreads
--enable-postproc --enable-swscale

2. xine-lib-1.1.16.3 release
[full download]
[english download]
Description: xine-lib 1.1.16.3 release
Shared xine-lib compiled against ffmpeg 0.5

configure notes:
configure --prefix=/usr --with-external-ffmpeg --disable-gnomevfs

3. gxine 0.5.901
[download]
Description: Not a required install. Existing versions will work just fine.
This version of gxine was compiled against xine-lib 1.1.16.3. There's
already one listed on puppy package manager. I'm using this since the
fullscreen mode works for me with the patched jwm.

configure notes:
configure --prefix=/usr --disable-mozjs --disable-ffjs --without-hal
--without-dbus

And before someone asks, I should mentioned that libamr (for 3gp) is not
compiled in as it is deemed non-gpl'ed.

Rgds

ttuuxxx · Posted: Tue 07 Apr 2009, 08:31 Post subject:

Thats excellent Patriot does ffmpeg/xinelibs come with the dev files?
Thanks again
ttuuxxx

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm ...

Yes, the dev header files are included. Dev files are also in xine-lib-english version but the docs/locales are removed. The rest are full versions.

Rgds

zigbert · Joined: 29 Mar 2006 Posts: 5562 Location: Valåmoen, Norway

Patriot
Thanks for the packages!

Sigmund

disciple · Posted: Sun 30 Aug 2009, 05:19 Post subject:

Thanks for this Patriot.

Can anyone tell me how to compile against it properly? Unlike the older versions it has a subfolder of header files for each ffmpeg library. When I try to compile something (dvdstyler) against it, it fails because it can't find the header files. I tried just moving them all out of their subfolders, and it compiled OK, but then the executable ended up dependent on the .so.51 libraries as well as the .so.52 libraries... except it actually wanted the .so.52 libraries for both... I don't know Rolling Eyes

Wait... maybe I just need to delete the header files from puppy's inbuilt ffmpeg first. I'll try that when I get a chance.

ttuuxxx · Posted: Sun 30 Aug 2009, 05:31 Post subject:

disciple · Posted: Sun 30 Aug 2009, 08:46 Post subject:

But do you know how I'm supposed to tell it to look in those subfolders for all the headers? Or do you think it would know, and just got confused by something in the old headers?

ttuuxxx · Posted: Sun 30 Aug 2009, 09:04 Post subject:

technosaurus · Joined: 18 May 2008 Posts: 4134

the code name "bike shed" reminded me of an old issue in software development.... It refers to having the biggest debates over the smallest issues.

Start at http://www.bikeshed.com and follow the rabbit hole back to the original discussions.

I wish I had remembered it when Warren was doing 4.2. It may have helped put things into perspective.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

It's been a while since I did this and I've been using them since I made the binaries. Currently, on puppy 4.12 with ffmpeg 0.5 + xine-lib 1.16.3 + stock gxine 0.5.9 ... Didn't quite like the tray feature in newer gxine ...

The dependencies between gxine and ffmpeg is through xine-lib. If only ffmpeg is updated, it will bork certain xine-lib's functions and further affects certain gxine functions. The best is to have matching binaries, ffmpeg -> xine-lib -> gxine. That's why I've provided the pets as such ...

To be clear, they were made to fulfill my requirements and I have encountered zero problems with it. If they do not fulfill yours, then the sources are freely available .....

To advanced users/developers:
If you're having issues with ffmpeg headers (like your compiled apps got confused with the headers), look for /usr/lib/ffmpeg (typo correction: should be /usr/include/ffmpeg). If its there, then its the older ffmpeg headers. Some apps looked in there and then skip checking for newer ones. New ffmpeg have changed the folders (from what I've seen). Remove that folder (or make a backup) and try compiling your apps again ...

To others:
I'm interested to know what kind of realmedia / flv files borks gxine. My rm+ra+rmvb and flv files all plays just fine ... If you have a problematic sample media, please open another thread and point me to it ...

Rgds

._.

BarryK · Posted: Sun 30 Aug 2009, 19:03 Post subject:

I went through the exercise of testing ffmpeg 0.5 and latest xine-lib awhile back. However got very patchy results testing my collection of video and audio files.
You need a collection of files to test on, a representative selection of what users will have. Such as .flv, .avi, .rm, .wmv, .ram, etc.

My old ffmpeg is the only one that plays them all nicely.

Hmmm, maybe I should upload my test suite.

Peterm321 · Joined: 29 Jan 2009 Posts: 209

disciple · Posted: Wed 02 Sep 2009, 01:42 Post subject:

For the record, all I had to do was delete /usr/include/ffmpeg, then it automatically found the new headers.

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

disciple · Posted: Sun 06 Sep 2009, 04:21 Post subject:

Also, just in case anyone else tries including this in an .sfs addon - any files that are also in the livecd will not work - the ones from the livecd will show up. This includes the pkgconfig files and symlinks like libavcodec.so, so you'll actually need a .pet or whatever anyway, to provide these files. And if you create them manually you have to run ldconfig afterwards.