Guido Scholz wrote: > a lot of distibutions provide a *-qt4 version of the Qt development > tools moc, uic, lupdate and lrelease. This means you can use moc-qt4, > uic-qt4, lupdate-qt4 and lrelease-qt4 instead. A check for their > availability may help. > > I don't know how scons handles such use cases but under > autoconf/automake it is quite easy to get around such trouble by using: > > AC_PATH_PROGS(UIC, uic-qt4 uic, no, [$PATH:$QTDIR/bin]) > > The first search matches "uic-qt4", if not found the search continues > for "uic". To set QTDIR properly can also help here. > > Hi!
That's nearly the same like we're doing in qt4.py already. Here's the current flow (IIRC): 1. Is QTDIR set? If yes, use it to determine the paths of uic etc. 2. If not 1: Look for "moc-qt4". If found, determine the path for moc-qt4 and use this as a hint for QTDIR. 3. Look for tools like lupdate, uic etc. with the help of QTDIR I suppose this should work as long as you don't set your QTDIR to the location of QT3. It would be nice to know the more about the cases in which scons fails to detect the correct version of uic/qtdir. I've tried a parallel installation of QT3/QT4 yesterday (without setting QTDIR) and it worked without a problem, so i'm pretty much interested in cases where it fails! - Sebastian ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Hydrogen-devel mailing list Hydrogen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
