Re: Qt rcc absolute path - Re: Getting ready to put out a 4.6 release candidate

[Ethan M. <merritt@u.washington.edu>]

On Friday, January 06, 2012 07:11:35 am Petr Mikulik wrote:
> During make, I see:
> 
> /usr/src/packages/BUILD/qt-everywhere-opensource-src-4.7.1/bin/rcc: Command 
> not found
> make[3]: *** [qrc_QtGnuplotResource.cpp] Error 127
> 
> and similarly for lrelease. 
> 
> Directory
>         /usr/src/packages/BUILD/qt-everywhere-opensource-src-4.7.1
> does not exist; rcc and lrelease are directly in /usr/bin/.
> 
> 
> Is this a bug in pkg-config? Here is what I get with pkg-config:
> 
> $ pkg-config --variable=rcc_location QtCore
> /usr/src/packages/BUILD/qt-everywhere-opensource-src-4.7.1/bin/rcc
> 
> $ pkg-config --variable=uic_location QtCore
> /usr/bin/uic

Sure looks like a pkg-config error to me.
What does it produce if you type:
  pkg-config --variable=moc_location QtCore


The reason I was adjusting the configure.in script section for Qt was
that Mojca and I also ran into pkg-config bugs.  The *.pc files shipped
with qt 4.6.3 (Mandriva 2010) fail to define rcc or lrelease at all;
instead they shipped a file /etc/profile.d/60qt4.sh that explicitly
adds a directory to $PATH.   But in qt 4.7.0 (Mandriva 2011) they
switched back to defining these in QtCore.pc just as they always had
for moc and uic:
  moc_location=/usr/lib/qt4/bin/moc
  uic_location=/usr/lib/qt4/bin/uic
  rcc_location=/usr/lib/qt4/bin/rcc
  lupdate_location=/usr/lib/qt4/bin/lupdate
  lrelease_location=/usr/lib/qt4/bin/lrelease

> Among others, the following libraries are installed:
> libqt4-devel-4.7.1-154.1
> qt3-devel-3.3.8b-87.11
> qt3-3.3.8b-87.11
> 
> It's on OpenSUSE 11.1 with KDE3.

Hmm.  I can see that there would be some trickiness required if the
same QtCore.pc file is supposed to handle parallel simultaneous 
installations of qt3 and qt4.  But yours seems to describe only qt4,
though it gets those two definitions wrong.  The gnuplot configure
script could test first for "rcc" and "lrelease" being in the current
path (that might handle Mojca's problem case also).  But again you
might run into interesting problems if you have both the qt3 and qt4
devel packages installed.

Anyhow, these are exactly the sort of platform-specific build problems
that the -rc1 is intended to shake out.  So I guess the plan is 
working even though -rc1 isn't yet announced :-)

	Ethan


-- 
Ethan A Merritt
Biomolecular Structure Center,  K-428 Health Sciences Bldg
University of Washington, Seattle 98195-7742