Georg Baum <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > Georg Baum <[EMAIL PROTECTED]>
| > writes:
| > | My opinion: For qt4: yes, since it would not work with moc3. For qt3
| > | probably not anymore (moc4 seems to work for qt3 just well, and if qt2
| > | is still on the system then it is probably too old anyway).
| >
| > But if we take for granted that the system is correctly installed.
| > Will it then matter? Cannot we just trust the information that
| > pkg-config gives us?
|
| I think so, but pkg-config does not give us moc and uic.
No, but does it have to?
We know that if qt-mt is installed, then moc and uic is there as well.
They can only have a few valid names. (My guess is moc-qt3 or moc)
and when they exist they also must have the correct version.
(and if we guess wrong you can always set the envir variable yourself
MOC='xxx')
| >
| > | Apart from that moc and uic are not always installed in $PATH, but in
| > | $QTDIR/bin.
| >
| > I would have thought that they were on the path anyway.
|
| Me too, but on suse moc3 and uic3 are not in the path. It seems that this
| changes with qt4.
uic3 is something completely different.
(at least on my qt4 setup, there it is a tool to convert qt3 version
ui files to qt4 version)
also easy enough to do a
QT3_PREFIX=`pgk-config --variable=prefix qt-mt`
POSSIBLE_MOC=$(QT3_PREFIX)/bin/moc
--
Lgb
