On 7/30/07, Dan Dennedy <dan at dennedy.org> wrote: > I just fixed this, and the prefix can now be obtained via pkg-config as: > > pkg-config --variable=prefix mlt-framework
Using pkg-config by KDEnlive build system woudn't be good for me and others using kdenlive-builder because system wide pkg-config would know nothing about MLT installed in some directory in a user's homedir. The problem in my case is that KDEnlive build system in fact discovers where my MLT installation is located: $ pwd /home/olo/misc/soft/Graphics/KDEnlive/kdenlive-dev-helpers/kdenlive $ grep -i mlt Makefile* Makefile:KDE_XSL_STYLESHEET = /usr/share/apps/ksgmltools2/customization/kde-chunk.xsl Makefile:LIBMLT_CFLAGS = -I/home/olo/build/kdenlive.2007-07-31_14_16/include -I/home/olo/build/kdenlive.2007-07-31_14_16/include/mlt -D_REENTRANT Makefile:LIBMLT_LIBS = -L/home/olo/build/kdenlive.2007-07-31_14_16/lib -lmlt Makefile.in:LIBMLT_CFLAGS = @LIBMLT_CFLAGS@ Makefile.in:LIBMLT_LIBS = @LIBMLT_LIBS@ And the KDEnlive binary is correctly linked with those. The same prefix (/home/olo/build/kdenlive.2007-07-31_14_16) is specified for all 4 source trees that are built: ffmpeg, mlt, mlt++, kdenlive. KDenlive binary properly loads the dynamically linked MLT libraries, as debugging with LD_DEBUG indicates. But KDEnlive still complains that it cannot locate MLT libraries on startup. That's the problem. And it has worked previously. -- Best Regards, Aleksander Adamowski http://olo.org.pl
