On Wednesday 01 September 2010 04:32:47 Timothy Pearson wrote:
> > On Tuesday 31 August 2010 13:57:26 Serghei Amelian wrote:
> > [...]
> >
> >> PS Maybe is better ideea to switch entire trinity project to cmake build
> >> system?
> >
> > I created a minimal cmake script, which is able to compile and install
> > tqt.
>
> Thanks!
>
> > For testing/using it, put CMakeLists.txt in root of tqtinterface, then
> > run follow commands:
> >
> > cmake -DCMAKE_INSTALL_PREFIX=/usr
> > make
> > make install DESTDIR=/tmp/test
> >
> > For verbose mode, you must run "make VERBOSE=1"
> >
> > Note that i do not tested if the resulted library is correctly built
> > (yet).
>
> Please find the list of files it should create and install attached.  Note
> that this is from the SVN HEAD revision, so it may contain a few more
> files than your Cmake script created.
>
> > Feedback are welcome.
>
> Good first steps!
>
> If you decide that you want to convert all of Trinity to Cmake (which
> would be *much* appreciated by the developers here! ), converting arts and
> kdelibs next would be my suggestion.  When you convert each module to
> Cmake, I will add the new Cmake files to each module in parallel with the
> existing Automake system. 

This is big task, but i will try :) The good thing is that cmake have builtin 
support for Qt3 and KDE3, this will help a lot.

> I can provide you with any information you 
> need, such as lists of installed files, etc. for verification.
>
> Do you have KDE SVN access?

I'm in sync with svn repo with "svn co 
svn://anonsvn.kde.org/home/kde/branches/trinity/dependencies/tqtinterface", 
I'm not sure if is correct.

> Thanks!
>
> Tim

PS You want keep qtq headers directly in /usr/include? I prefer to separate it 
from system headers, like /usr/include/qtq

-- 
Serghei