{"id":335,"date":"2006-09-21T22:08:18","date_gmt":"2006-09-22T05:08:18","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/ffmpeg-autobuilds\/"},"modified":"2009-02-24T10:36:03","modified_gmt":"2009-02-24T18:36:03","slug":"ffmpeg-autobuilds","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/ffmpeg-autobuilds\/","title":{"rendered":"FFmpeg Autobuilds"},"content":{"rendered":"

I have been sitting on this for at least a month. As brainstormed in this post<\/a>, I have developed a system on a spare, headless, always-on x86 Linux box that automatically updates its FFmpeg SVN copy and compiles it with 6 different gcc versions, essentially the latest in each of the 2.95, 3.2, 3.3, 3.4, 4.0, and 4.1 series. That’s all working quite well. The part that I’m trying to resolve right now is what to do with the results. I would like to aggregate the results into a concise format for easy web reading. Plus, it would be good to have a history of build successes\/failures. I think an RSS aggregation would be useful as well. And for bonus points, some halfway intelligent system that figures out which warnings occur in all or most builds. This would reveal good code janitor work for aspiring FFmpeg developers.<\/p>\n

This is just the first phase. Of course, I want to add functional tests later, such as the standard regression. I am still trying to get the infrastructure up.<\/p>\n

Related post:<\/p>\n