On Sun, Mar 18, 2012 at 2:39 PM, Brian Matherly <[email protected]> wrote: > Dan, > > I have a new proposed version of build-melt.sh. > > https://github.com/pez4brian/build-melt/blob/master/build-melt.sh > > Here is the diff: > https://github.com/pez4brian/build-melt/commit/5702f4ca3718d4bf6fc0dccb68b7625d3b6be27e
seem my comments there > > These modifications add the ability to specify ffmpeg or libav and you can > also specify a branch to use (by extending the FFMPEG_REVISION variable). > With this script, I was able to test all ffmpeg and libav branches using the > following configurations: > > # FFMPEG master branch > FFMPEG_HEAD=1 > FFMPEG_PROJECT="ffmpeg" > > # FFMPEG 0.5 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.5" > FFMPEG_PROJECT="ffmpeg" > FFMPEG_SUPPORT_LIBVPX=0 > > # FFMPEG 0.6 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.6" > FFMPEG_PROJECT="ffmpeg" > > # FFMPEG 0.7 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.7" > FFMPEG_PROJECT="ffmpeg" > > # FFMPEG 0.8 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.8" > FFMPEG_PROJECT="ffmpeg" > > # FFMPEG 0.9 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.9" > FFMPEG_PROJECT="ffmpeg" > > # FFMPEG 0.10 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.10" > FFMPEG_PROJECT="ffmpeg" > > > # Libav master branch > FFMPEG_HEAD=1 > FFMPEG_PROJECT="libav" > > # Libav 0.5 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.5" > FFMPEG_PROJECT="libav" > FFMPEG_SUPPORT_LIBVPX=0 > > # Libav 0.6 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.6" > FFMPEG_PROJECT="libav" > > # Libav 0.7 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.7" > FFMPEG_PROJECT="libav" > > # Libav 0.8 branch > FFMPEG_HEAD=0 > FFMPEG_REVISION="origin/release/0.8" > FFMPEG_PROJECT="libav" > > Let me know what you think. I can take it another direction if you have a > better idea. > > > Also, would you be amicable to the idea of creating a new git repository for > MLT scripts (the ones from the Wiki) and maybe some other misc. scripts that > I'll need for all the automated tests? > The purpose of the scripts was to make it convenient and easy for users. Does putting them into a git repo defeat that? We can make links to the git-web head's version, but unlike the wiki, which makes it download, it just opens in the browser for me, e.g. http://mltframework.org/gitweb/mlt.git?p=mltframework.org/mlt.git;a=blob_plain;f=configure;hb=HEAD -- +-DRD-+ ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
