[Clfs-dev] CBLFS -- query about cmake & qt4

Joe Ciccone jciccone at gmail.com
Tue Apr 7 17:15:43 PDT 2009


db m wrote:
> Greets,
>
> I just stumbled across a package (lmms) that uses the cmake
> build system for compilation - the package requires qt4, but
> cmake fails to find the qt4 qmake binary...
>
> This is likely to happen only if you have qt4 installed in /opt
> and you have qt3 installed in /usr -- the cmake control files
> (/usr/share/cmake-{version)/Modules) expect to find qt4 in
> /usr, and failing that, will walk the current $PATH looking for
> a valid qt4 qmake binary named 'qmake-qt4' or 'qmake4' - we
> do not create this during the CBLFS qt4 build procedure.
>
> We do set the QT4DIR variable (ignored by cmake) and include
> /opt/qt4/bin in $PATH, but cmake must find qmake-qt4 (or qmake4) 
> in $PATH (these can be symlinks to /opt/qt4/bin/qmake) or else the
> cmake system will error out.
>
> Although I could update the wiki page to add such a symlink
> and effectively fix this boofle, it occurs to me that in the case
> of a multilib build....where /opt/qt4/bin/qmake is a symlink back
> to  /usr/bin/multiarch_wrapper.....such an approach is not correct.
>
> i've put off touching the wiki on this, and instead air the situation
> here hopeful of some advice with this....anyone have any ideas?
>   
I have yet to find a good solution for qt3 and qt4 existing on the same
system. I opted to just not install qt3 anymore and only put qt4 in. I
simply refuse to use cmake, it sucks.

I'm wondering if a custom wrapper should be written for qmake, moc, and
uic. It would be easy enough to do.




More information about the Clfs-dev mailing list