From: Mads B. D. <ma...@dy...> - 2008-12-12 08:49:37
|
fredag 12 December 2008 skrev Jean-Michel Pouré: > Before compiling Kdenlive, you should always remove any installed MLT > version, including pkgconfig files, especially if installed > in /usr/local. <commercial> A little "commercial" here: among the many small things the builder wizard does, one is that it will fiddle with PKG_CONFIG_PATH to fix this for you.... So, you can keep e.g. distribution installed packages of mlt while having your kdenlive environment in e.g. /usr/opt/whatever Using the "append date", you can keep several versions of kdenlive installed (good for e.g. regressions). And, you can put this in your path somewhere, to always run the newest kdenlive you have installed using the wizard (perhaps name it kdenlive_newest): ---------- #!/bin/bash PREFIX=`grep INSTALL_DIR $HOME/.kdenliveBuilderWizard.rc | cut -f 2` VER=`ls $PREFIX | grep -E '^[[:digit:]]{8}$' | tail -n 1` exec $PREFIX/$VER/bin/kdenlive_start "$@" ---------- So, kdenlive_newest will start your newest kdenlive install kdenlive_newest --version will report svn rev numbers for ffmpeg, mlt, mlt++ and kdenlive kdenlive_newest -g will start directly in debug mode, setup to create a crash log kdenlive_newest -n will just start it. In the source package for the wizard, there even is a script suited for cronjobs, to e.g. compile kdenlive every night. (kbw-action.sh) </commercial> Regards Mads -- Mads Bondo Dydensborg ma...@dy... http://www.madsdydensborg.dk/ Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music. --Kristian Wilson, Nintendo, Inc, 1989 |