All,
I have built and installed tqtinterface on Arch and I'm attempting to build
arts and I receive the following error:
<snip>
checking for Qt... libraries /opt/qt/lib, headers /opt/qt/include using -mt
checking for moc... /opt/qt/bin/moc
checking for uic-tqt... not found
configure: WARNING: No Qt ui compiler (uic) found!
Please check whether you installed Qt correctly.
You need to have a running uic binary.
configure tried to run and the test didn't
succeed. If configure shouldn't have tried this one, set
the environment variable UIC to the right one before running
configure.
Looking at my tqtinterface build directory, I find:
22:27 archangel:~/arch/pkg/trinity-notes/tqtest> find . -name "uic*"
./src/qtinterface/.svn/text-base/uic-tqt.svn-base
./src/qtinterface/.svn/prop-base/uic-tqt.svn-base
./src/qtinterface/uic-tqt
so uic-tqt got built, but apparently was not included by 'make install' into the
Arch package I created.
The tqtinterface package installed as follows:
22:15 archangel:~/arch/pkg/trinity-notes/arts> pacman -Ql tqtinterface
tqtinterface /usr/
tqtinterface /usr/bin/
tqtinterface /usr/bin/convert_qt_tqt1
tqtinterface /usr/bin/convert_qt_tqt2
tqtinterface /usr/bin/convert_qt_tqt3
tqtinterface /usr/bin/dcopidl-tqt
tqtinterface /usr/bin/dcopidl2cpp-tqt
tqtinterface /usr/bin/dcopidlng-tqt
tqtinterface /usr/bin/mcopidl-tqt
tqtinterface /usr/bin/moc-tqt
tqtinterface /usr/bin/tmoc
tqtinterface /usr/bin/tqt-replace
tqtinterface /usr/bin/tqt-replace-stream
tqtinterface /usr/include/
tqtinterface /usr/include/tqt/
tqtinterface /usr/include/tqt/Qt/
tqtinterface /usr/include/tqt/Qt/q3cstring.h
<snip>
but no uic-tqt interface. So it looks like this is a file I will need to
manually tell the Arch makepkg app to include in the package. Easy enough to do,
but:
"Where is 'uic-tqt' supposed to get installed to?" Which directory does it go in?
--
David C. Rankin, J.D.,P.E.
All,
After what appeared to be a successful build and install of kdelibs, I moved on
to configure kdebindings (I remembered --enable-closure). During the configure with:
trinity_prefix="/opt/trinity"
./configure --prefix=${trinity_prefix} \
--includedir=${trinity_prefix}/include/kde \
--mandir=${trinity_prefix}/share/man \
--infodir=${trinity_prefix}/share/info \
--with-extra-libs=${trinity_prefix}/lib \
--sysconfdir=/etc \
--localstatedir=/var \
--libexecdir=${trinity_prefix}/lib/kdebase-kde3 \
--disable-rpath \
--enable-closure
I received the following error:
<snip>
checking for rpath... no
checking for KDE... libraries /opt/trinity/lib, headers /opt/trinity/include
checking if UIC has KDE plugins available... no
configure: error:
you need to install kdelibs first.
If you did install kdelibs, then the Qt version that is picked up by
this configure is not the same version you used to compile kdelibs.
The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the
_same Qt version_, compiled with the _same compiler_ and the same Qt
configuration settings.
Aborting...
Huh? I did install kdelibs, and I didn't do anything (that I know of) to have it
use some other Qt, so I'm a bit stumped. I did install kdelibs as
trinity-kdelibs (if that matters - I'll check the provides() line), but the
package is installed:
00:33 archangel:/dat_e/david/bld/trinity/kdelibs/pkg> pacman -Q trinity-kdelibs
trinity-kdelibs 1218332-1.0
The full file list for the package is here:
http://www.3111skyline.com/dl/dt/trinity/filelists/kdelibs-filelist.txt
Any idea of what file isn't being located when UIC is checking for KDE plugins?
At least that way I can look and see if I have what it needs. Thanks.
--
David C. Rankin, J.D.,P.E.
I thought I had this sorted, but alas no...
The arts ./configure is failing to find TQt and issuing the following warning:
<snip>
checking for Qt... libraries /opt/qt/lib, headers /opt/qt/include using -mt
checking for moc... /opt/qt/bin/moc
checking for uic-tqt... /usr/bin/uic-tqt
checking whether uic supports -L ... yes
checking whether uic supports -nounload ... yes
checking if TQt is available... no
configure: WARNING: You are attempting to compile Trinity without the Trinity Qt
Interface installed. Please install libtqtinterface-dev and try again!
The configure completes successfully, but I'm concerned about the warning.
Looking at 'configure' itself, it seems to adjust for this with:
if ${kde_cv_tqt+:} false; then :
$as_echo_n "(cached) " >&6
else
<do other stuff>
So is this Warning OK? Obviously, Trinity isn't installed yet, so I suspect
that is producing the warning, but I want to check to make sure there isn't
something I need to fix before proceeding.
cmake completes fine on arts :)
--
David C. Rankin, J.D.,P.E.
Tim, All,
Just dropping a note to let you know I started a Trinity wiki page for Arch
Linux on the Arch wiki:
https://wiki.archlinux.org/index.php/Trinity
It is still in it's infancy, but there has been notable interest shown from the
user list. Once I'm through filling in the gaps, we can add a link here under
the distro specific information if you like. Cheers!
--
David C. Rankin, J.D.,P.E.
Hi Tim,
Most Trinity man pages seem to exist in paths such as
/usr/share/man/man1/k3b-trinity.1.gz but there are also
variants such as:
/usr/share/man/man1/kuickshow.1.gz
/opt/trinity/share/man/man1/gwenview.1
/opt/trinity/share/man/man1/kate-trinity.1
/opt/trinity/share/man/man1/kdesud.1.gz
Having drawn this to your attention here, is there any
additional follow up that you would like me to do?
I'm guessing that the last path format is best?
--Mike Bird
Ubuntu 10.10+Trinity
xine 1.2 from hg/debian site. Worked fine in 9.10.
xine-ui as well from there.
Compiled and xine-ui plays h264 on vdpau+pulse just fine.
compiled kaffeine:
a) src from trinity
b) vanilla 0.8.8
--without-xcb.
As soon as I enable vdpau it crashes. No matter what I set for sound, alsa,
pulse, none.
Since xine-ui works a charm (and mplayer, too for that matter) I suspect
something in the kde build environment to be fishy. (Possibly that wrong qt
package? Is maybe the entire 3.5.12 build hosed?)
Appreciate pointers.
Dex
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
I'm feeling really stupid. I have an installation of Trinity on Squeeze
where the user uses Icedove for email. For some reason, it wants to
open PDF files in GIMP. I see the same thing in other Gnome
applications like Evolution.
I've gone to Icedove preferences and tried to change the application
type and clicking on other . . . does not produce a dialog box to select
an application (like KPDF or acroread). I installed kgtk-config-icedove
but that did not help. I even installed Nautilus and tried setting the
application association there. That at least presented KPDF as an
option in Evolution but not in Icedove. I installed gconf-editor but
that does not seem to address application associations.
Short of finding which defaults.list file it is looking at and manually
editing it or manually setting it in mimetypes.rdf, how does one set
this in a Trinity only environment (in that Gnome desktop is not
installed)? Thanks - John
Guys,
Just a quick sanity check. I have the Arch Linux package for tqtinterface
building, but I saw a few headers that were not found during cmake:
Checked out revision 1217590.
==> SVN checkout done or server timeout
==> Starting cmake...
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- checking for 'Qt'
-- Performing Test HAVE_PATCHED_QT3
-- Performing Test HAVE_PATCHED_QT3 - Success
-- found patched Qt, version 3.3.8
-- Looking for qinputcontext.h
-- Looking for qinputcontext.h - not found
-- Looking for qinputcontextfactory.h
-- Looking for qinputcontextfactory.h - not found
-- Configuring done
<snip>
Are the 'not found' headers OK, or do I have a build problem on my end? Sorry
if this is a stupid question, but I'm still feeling my way through the initial
build :)
--
David C. Rankin, J.D.,P.E.
Guys, Gals,
After pulling my hair out getting pykde to build correctly with the old kde3
removed, I patched built and installed qt3-3.3.8c, reinstalled kde3, built pykde
and I'm now moving forward through the trinity svn build order.
Can I do this?
My plan is to rebuild pykde as I get the trinity packages built and put in
place. Any gotchas?
--
David C. Rankin, J.D.,P.E.
On 01/26/2011 03:08 PM, Neil Youngman wrote:
> Different Wikis have different markups. The Trinity Wiki is FOSWiki. See
> http://foswiki.org/System/TextFormattingRules for FOSWiki's markup.
>
> I have corrected the headers to use FOSWiki markup.
>
> HTH
>
> Neil Youngman
>
That's the ticket! Thanks Neil. I'll go grab the foswiki reference.
--
David C. Rankin, J.D.,P.E.