lmc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmc-dev] MovieFly on FreeBSD (long)


From: lmc-dev
Subject: Re: [lmc-dev] MovieFly on FreeBSD (long)
Date: Sun, 7 Aug 2005 18:03:14 +0200
User-agent: KMail/1.7.2

Hi Martin,

so, we have two problems:
1. propper installation support for FreeBSD
2. moviefly won't open .amc files

Here: lets get onto the installation problem.

I have modified the build system and changed some functionality and would like 
you to download a pre-release from the following url and test it. 
If you agree, once that works I'll officially upload a new version to 
Savannah.

The URL is:
http://www.master-ai.uni-karlsruhe.de/~merkosh/lmc/unofficial

On Monday 01 August 2005 05:09 am, address@hidden wrote:
> 1. Required dependencies
[...]

It seemed you did not run into problems getting the required packages. I am 
not familiar with FreeBSD, is there any additional BSDish way of specifying 
the required packages? Else I'll roughly add the following to the 
documentation:

--
use "pkg_add -r" on "qt" (qt 3.3), "qmake", "eject", "transcode", "gmake", 
"py23-qt" and install the required packages
--

> 2. Issues using ./configure

> 2.1 The first problem I stumbled into was configure's unability to find
> the python qt module. 

I'll add another note that the python executable must be accessible through 
the PATH under the name "python". (i.e. not pythonX.Y)

> 2.2 The second problem was configures unability to find the Qt files,
> starting with the message "checking for Qt... ls: /lib/libqt*: No such
> file or directory". Qt on FreeBSD gets installed into /usr/X11R6/, thus
> adding --with-Qt-dir=/usr/X11R6/ quickly resolved the issue.

I've added this already to the INSTALL file.

> 2.3 A problem I did not really solve was configure's test of the correct
> functioning of the qt environment -- I just inserted a the line
> 'bnv_cv_qt_test_result="succes"' at the appropriate place (somewhere
> around line 6369).

Auto*tool support for Qt is a cramp. I've tried using other macros during the 
week, but without much improvement. So now I'm debugging the macros I've used 
up until now.

I made changes to the BNV_HAVE_QT macros. Please specify the 
--with-Qt-dir=/usr/X11R6 flag to the configure script and see wether the test 
succeeds. If not, please send me the contents of the bnv_qt_test_*.out files.

> 2.3 Next thing I had to do was add
> "--with-sip=/usr/local/share/sip/qt/qtmod.sip" to the configure
> commandline in order to enable it to find sip.

The correct path would have been:
--with-sip=/usr/local/share

I've added /usr/local/share to the default search path. You should not need to 
specify it any more.

> Otherwise, I got:
>       "checking for sip include path... find: illegal option -- t
>       find: illegal option -- y
>       find: illegal option -- p
>       find: illegal option -- e
>       find: f: No such file or directory
>       find: /usr/share/sip: No such file or directory"
>
> There seems to be something wrong with the
>       sip_path=`find $i -type f -name qtmod.sip -print | sed "1q"`
> line in configure, resulting in the above error.

Hm. Can't explain that mistake. Lets check it again with the changes uploaded 
in pre-release 1.

> 3. Issues during compilation
>
> 3.1 After configure finished its job, I ran gmake -- only to be
> confronted with a bunch of messages like:

gmake == the "normal" GNU make?


[... lot of compilation problems ...]

Theoretically the compilation problems should not have anything to do with the 
"open file" problem, as this part is all done in pure Python. 
There is, however, a new configure switch --disable-listviewsort, which 
disables the compilation of the C++ module. The default Qt class is used 
instead. This causes the movie entries to be sorted alphanumerically. There 
is a config option to prepend zero's instead - as an intermediate solution 
when the C++ module does not work.
The Qt detection must still be successfull, though.

>       "In file included from sip_build/siplmcqtcmodule.cpp:9:
>       siplmcqtListViewSort.h:14: sipqtQListViewItem.h: No such file or
>       directory siplmcqtListViewSort.h:15: sipqtQListView.h: No such file or
>       directory
>       [...]"

>       "sip_build/siplmcqtListViewSort.cpp: In function `struct
>       PyObject * meth_ListViewSort_activatedPos(PyObject *, PyObject
>       *)':sip_build/siplmcqtListViewSort.cpp:840: `sipClass_QPoint'
>       undeclared (first use this function)",

After a successfull configure, please change into .../src/lmcqt and run:
$ make

and send me the compilation output.

> 3.2 Then, qmake failed because by default, no spec is set:
>
>       "/usr/local/bin/qmake -o listviewsort.mak listviewsort.pro
>       QMAKESPEC has not been set, so configuration cannot be deduced.
>       Error processing project file:
>       /usr/home/martin/lmc-0.12.3/src/lmcqt/listviewsort.pro"
>
> This could be solved by issueing the following on the command line:
>       export QMAKESPEC=/usr/local/share/qt/mkspecs/freebsd-g++

I've not considered special qmake flags up until now. Now, after qmake 
detection the it should mention special qmake flags "-spec freebsd-g++"
Otherwise, please send me your output to "uname -o".

> 3.3 The next thing that failed was this:
>
>       c++ -c -Isip_build -I/usr/local/share/qt/mkspecs/freebsd-g++ -I.
> -I../../../../../local/include -I/include -o listviewsort.o
>       listviewsort.cpp
>       In file included from listviewsort.cpp:23:
>       listviewsort.h:26: qlistview.h: No such file or directory
>       listviewsort.h:27: qstring.h: No such file or directory
>
> Adding -I/usr/X11R6/include to CXXFLAGS solved this one.

Hm. Actually freebsd-g++ should be an option to qmake. Lets see if compilation 
succeeds with pre1.


> 3.4 Then, the command
>       "c++ -Wl,-rpath,/usr/local/lib  -Wl,-rpath,/lib -pthread -shared
> -Wl,-soname,liblistviewsort.so.0 -o liblistviewsort.so.0.1.0
> listviewsort.o   -L/usr/local/lib -L/lib -lqt-mt"
> failed with the error: "/usr/libexec/elf/ld: cannot find -lqt-mt"

> Adding "--with-Qt-lib-dir=/usr/X11R6/lib" and
> "--with-Qt-include-dir=/usr/X11R6/include" to the configure command line
> did *not* solve this problem. Also, adding "-L/usr/X11R6/lib" to the
> CXXFLAGS had no effect.

> So I compiled the file by hand, adding -L/usr/X11R6/lib to the command.

Hm. Ok. 

> 3.5 The next command to fail was
>       "g++ -shared -o lmcqt.so siplmcqtcmodule.o
>       siplmcqtListViewSort.o  listviewsort.o -L/usr/X11R6//lib
>       -lqt-mt  -lSM -lICE  -L/usr/X11R6/lib -lX11 -lXext -lXmu
>       -lXt -lXi  -lm  -lpthread -L.",
> with error:
>       "/usr/libexec/elf/ld: cannot find -lpthread"
>
> This was solved by removing the -lpthread from the appropriate
> "Makefile*" files.

Hm. (tm)
Please try again, otherwise I'll try removing libpthread from the Makefile.am.

> 4.

> Installation went fine, but first I tried a prefix different from
> /usr/local (where python is installed) which resulted in the unability
> to run the program.

How did you prefix it? Both --prefix and DESTDIR works for me, BUT:
Python might not look for modules in non standard module directories and you 
might get errors like: Settings.py not found.

You can set the PYTHONPATH environment variable to the site-packages directory 
where you installed lmc. That should work, too.

> Also, I did only run the program for a short time, but it seems to
> function well except for the fact that I cannot open any .amc-Files,
> even ones created with MovieFly -- but this is another problem.

Right, I'll write you a mail on that in a jiffy.

> I hope this may help MovieFly to support FreeBSD out of the box in a
> future version.

I hope I'll get it to work, too. Thanks for your support.

Ciao
Uwe
-- 
Humpty Dumpty was pushed.

Attachment: pgpuxFwNsDclO.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]