[flyingrat]

Most work on the FFmpeg version bump to v1.1 is done. I need some advice here:

1. What's the normal way of working with xbmc and git (e.g: "fork, apply ffmpeg 1.1 changes, test, change, test, pull request") ?
   
2. Which branch shall I fork, current master or the frodo release?
   
3. How do I find and invite developers that can test the fork on other platforms?
   
4. What is the best way to find a "buildable" version of the master branch for osx?

Thanks in advance! /Regards, Lars.

[davilla]

1) "fork, apply ffmpeg 1.1 changes, test, change, test, pull request"
2) current master, this will never go into frodo
3) you don't, we see all PRs.
4) eh ? same as the others, current master

make sure the patches in lib/ffmpeg/patches are up to date.

[flyingrat]

Hi Davilla, thanks for the update! Some follow-up questions:

"3. How do I find and invite developers that can test the fork on other platforms?"
you don't, we see all PRs.

Ok, so there is no need to test other platforms before the PR then?

"4. What is the best way to find a "buildable" version of the master branch for osx?"
eh ? same as the others, current master

Sorry, forgot to explain. I've had quite some trouble in the past with some branches that didn't build correctly on osx. I was wondering if xbmc has a build-server with nightly builds you can check for a particular platform (osx in my case) ?

"make sure the patches in lib/ffmpeg/patches are up to date."

Sorry, no exiting lib/ffmpeg/patches directory. Maybe it was created by a xbmc maintainer?
--

Regards, Lars.

[davilla]

Well testing on all platforms is mandatory before the PR will be injected. Once this becomes a real PR then I'm sure some XBMC will jump in to test on various platforms.

We go have a buildbot that builds the nightlies and we can tell it to target any github repo/branch.

see the existing lib/ffmpeg/patches ( https://github.com/xbmc/xbmc/tree/master...eg/patches ) if this is not addressed, then the PR will get ponked This dir is all the XBMC patches we make to ffmpeg. It MUST be current and kept up to date.

[flyingrat]

> We go have a buildbot that builds the nightlies and we can tell it to target any github repo/branch.
Great, where do you find the status page for the nightlies?

> This dir is all the XBMC patches we make to ffmpeg. It MUST be current and kept up to date.
Well, I presume the directory only includes ffmpeg patches and since we are starting out with a fresh version of ffmpeg, the directory will be empty for now.

Btw, here is the fork with the FFmpeg version 1.1.2: https://github.com/FlyingRat/xbmc-ffmpeg-v1.1-bump.git

[davilla]

> This dir is all the XBMC patches we make to ffmpeg. It MUST be current and kept up to date.
Well, I presume the directory only includes ffmpeg patches and since we are starting out with a fresh version of ffmpeg, the directory will be empty for now.

Wrong assumption, that ASSumes that all those patches are in fact in the updated ffmpeg which is not true.

[Memphiz]

Life could be so easy

[flyingrat]

Life could be so easy

Yes, it would be if Mr. Murphy didn't hang around...