trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: August 2011

Re: [trinity-devel] Building arts 3.5.12 from tarball (success)

From: Francois Andriot <francois.andriot@...>
Date: Wed, 24 Aug 2011 19:11:41 +0200
Le 24/08/2011 18:54, LD a écrit :
> I'm trying to compile Trinity on a multilib Linux from scratch. I tried several
> times to compile arts, googled, looked into the archives of this mailing list.
> I had the idea to patch the Makefile in qtmcop. And it compiled. But the same
> problem arises with kdelibs and there is a lot of calls to 'moc', in a lot of
> makefiles.
> So I'm feeling a little stupid now and I'm wondering what to do.
> If someone can see where I'm going wrong...
>
> Details below:
>> Making all in qtmcop
>> make[2]: Entering directory `/usr/src/trinity/arts/qtmcop'
>> /usr/share/qt/bin/moc ./qiomanager_p.h qiomanager_p.moc
>> Qt meta object compiler
>> moc: Too many input files specified
Hello,
unless I do not remember well, the compilation process should not use 
"moc" from QT directly, but instead use "moc-tqt" from TQT ...
These 2 tools do not use the same syntax, that's why it's failing here.

I suppose it's because /opt/trinity/bin should be the first in your $PATH.
Once you have compiled & installed TQT to /opt/trinity/ , you should set 
your environnment to use it BEFORE the standard path.

You may have seen a warning during the ARTS "./configure", saying 
something like "you are trying to compile without TQT". It should NOT 
occur, except when compiling TQT itself.
Until you see this warning in the ./configure , you cannot compile 
correctly.

Example of my compilation commands:
$ export PATH=/opt/trinity/bin:$PATH
I've noticed that for most Trinity components I must also set the 
LDFLAGS variable or else linking fails: (adjust the directories as needed)
$ export LDFLAGS="-I/opt/trinity/include -L/opt/trinity/lib64"
Then I can run ...
$ ./configure XXXXXXXXX
$ make .......

Note that I do not set other environment variables and I do not have a  
special ld.so.conf ...
These 2 variables are sufficient on my computer.

Good luck !