All,
The current mlt++ source Makefile requires that the 'test' directory be compiles as part of the build. This fails on Arch. I have disabled the build of the 'test' dir files with:
sed -i '/$(MAKE) -C test $@/d' Makefile
Is there any reason they should be built by the current Makefile to begin with? Isn't that something that is normally done by the user AFTER the package is installed? Since the 'test' Makefile requires -lmlt++ and that lib isn't installed until the package is installed - this will cause a build failure every time.
The current mlt++ source Makefile requires that the 'test' directory be compiles as part of the build. This fails on Arch. I have disabled the build of the 'test' dir files with:
sed -i '/$(MAKE) -C test $@/d' Makefile
Is there any reason they should be built by the current Makefile to begin with? Isn't that something that is normally done by the user AFTER the package is installed? Since the 'test' Makefile requires -lmlt++ and that lib isn't installed until the package is installed - this will cause a build failure every time.
Does building mt++ require first building mt? I want to help but I am unable to build mt. Looks like mlt can't find the tqt header files....
Darrell
On 03/30/2012 12:39 PM, Darrell Anderson wrote:
Does building mt++ require first building mt? I want to help but I am unable to build mt. Looks like mlt can't find the tqt header files....
Yes you need mlt build because mlt++ calls mlt-config, but this problem is an obvious "Chicken or the egg issue" ... and the answer is "egg".
The build for the subdir "test" in mlt++ needs libmlt++ already installed on the system. Think about it, your are building mlt++, that lib isn't on your system until you finish the package and install.
This looks like one of those:
(1) "Let's add the 'test' dir to the source so people will have it as a reference..."
deals and then in some automagic/autoconf/whatever run later, the Makefile got generated saying:
(2) "Hey, I found a subdir called 'test', let's add a directive to build 'test'"
and since they were building it on a system where mlt++ was already installed,
(3)the automagic files found the libmlt++ lib and included it in the library flags to build 'test'.
This looks like exactly what happened to me, but I need someone to confirm this because "I don't know...." :)
Give this a try on mlt (i686 only):
./configure \ --prefix=${TDEDIR} \ --enable-gpl \ --disable-sox \ --disable-qimage
Does building mt++ require first building mt? I want to
help but I am unable to build mt. Looks like mlt can't find the tqt header files....
Yes you need mlt build because mlt++ calls mlt-config, but this problem is an obvious "Chicken or the egg issue" ... and the answer is "egg".
Just a guess, but sounds as though mlt++ is self-referencing. I don't know the correct terminology but qt3 does the same thing. Perhaps pattern the mlt++ build script similar to the (t)qt3 build scripts.
Darrell
-
Darrell Anderson -
David C. Rankin