[flyingrat]

@flyingrat, need the 3 steps, for create one install for win os.

I've read the wiki, but thanks anyway! I've also debugged and altered necessary build scripts to make the new ffmpeg libs to build in on win32 thus I'm quite aware of how the build scripts work (or don't work ). If you refresh your local xbmc repo you only need (AFAIK) BuildSetup.bat thus the question still remains, how is the Win32 Nightly Builds performed?

[vicbitter]

ffmpeg 1.1.3 has been released... The XBMC patches ported to 1.1.2 still work on 1.1.3...

[flyingrat]

ffmpeg 1.1.3 has been released... The XBMC patches ported to 1.1.2 still work on 1.1.3...

Thanks for the update! I'll update the fork and will let you know when it's done...

[flyingrat]

You can clearly see the 1.1.3 tag in Github but I couldn't find any release info on the ffmpeg home page. Where are new minor releases announced normally? (in the mailing lists??)

[matander]

You find the "release information" a bit down this page: http://ffmpeg.org/download.html
where they also link to the changelog http://git.videolan.org/?p=ffmpeg.git;a=...g;h=n1.1.3

I think one important thing might be security fixes: http://www.us-cert.gov/ncas/bulletins/SB13-063

[jjd-uk]

You can clearly see the 1.1.3 tag in Github but I couldn't find any release info on the ffmpeg home page. Where are new minor releases announced normally? (in the mailing lists??)

See http://ffmpeg.org/download.html#releases

[flyingrat]

You find the "release information" a bit down this page: http://ffmpeg.org/download.html
where they also link to the changelog http://git.videolan.org/?p=ffmpeg.git;a=...g;h=n1.1.3

I think one important thing might be security fixes: http://www.us-cert.gov/ncas/bulletins/SB13-063

---

You can clearly see the 1.1.3 tag in Github but I couldn't find any release info on the ffmpeg home page. Where are new minor releases announced normally? (in the mailing lists??)

See http://ffmpeg.org/download.html#releases

Thanks for the pointers! What did I think of, it's quite obvious that this info is located half way down on the download page and not in the news section.

[Memphiz]

buildbot always builds from an empty dir. So the full circus everytime.

[flyingrat]

FFmpeg n1.1.3 + xbmc add on patches seems fine although I've only had time to test build the win32 environment tonight. Note: work is done locally, i.e. no changes pushed to github yet...

Btw, I'm still having a lot of problems with DownloadBuildDeps.bat which results in missing or corrupt libs. This is due to the lack of error checking in dlextract.bat when downloading from non working mirror sites.

[Karlson2k]

flyingrat, see https://github.com/xbmc/xbmc/pull/2385

[flyingrat]

flyingrat, see https://github.com/xbmc/xbmc/pull/2385

Great, exactly what I was looking for! Thank you very much, sir.

[flyingrat]

Fork "https://github.com/FlyingRat/xbmc-ffmpeg-v1.1-bump" is now updated with FFmpeg 1.1.3 including xbmc add on patches. I'll add the win32 changes as soon as I get my f*n vmware partiton to work again . Most changes in the xbmc tree (except ffmpeg) are temporary labeled with @FFMPEG113.

Xbmc add on patches are now managed in the FFmpeg fork "https://github.com/FlyingRat/FFmpeg-with...om-patches", in the separate branch "n1.1.3-xbmc".

Please test and/or review, feedback is welcome!

[flyingrat]

flyingrat, see https://github.com/xbmc/xbmc/pull/2385

Great, exactly what I was looking for! Thank you very much, sir.

What's the best way to add the PR above to the fork "FlyingRat/xbmc-ffmpeg-v1.1-bump" without causing to much trouble upstreams, will for example "git cherry-pick" do the work even though it creates new commits?

[Ace]

I can imagine at least these two ways: cherry-pick it and drop it before you open the pr at xbmc's repo or get the diff, patch it locally and add the BuildDependencies folder to the ignore list.

[flyingrat]

Win32 changes and Karlson2k's error checking added to the fork. I'm gonna perform some testbuilds on win32 and osx, can I tempt anyone to run a test build of the RPI??