Re: Qt terminal status?

[Daniel J S. <dan...@ie...>]

On 08/22/2012 05:03 AM, Petr Mikulik wrote:
>> What is the status of the Qt terminal?  It easily builds and works on
>> linux systems.
>
> Not here, I still see the error I reported in January:
>
> ***************************************
>
> 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
>
>
> 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.
>
> ***************************************
>
> I think the problem is in  configure.in  which contains this check:
>
>    RCC=`$PKG_CONFIG --variable=rcc_location QtCore`
>    if test x"$RCC" = x ; then
>      if test x"$QT4LOC" != x ; then
>          RCC=$QT4LOC/bin/rcc
>      else
>          RCC=rcc
>      fi
>    fi
>
> I think it should be replaced by
>    if "$QT4LOC/bin/rcc exists"
>    then RCC=$QT4LOC/bin/rcc
>    else RCC=rcc
>
> and similarly for lrelease.

If the

if test x"$QT4LOC" != x

is removed and QT4LOC happens to not be defined, then the line

     then RCC=$QT4LOC/bin/rcc

will fail during configure.  So you might have to place the proposed 
test one level deeper inside the check for $QT4LOC.

How exactly you get

   /usr/src/packages/BUILD/qt-everywhere-opensource-src-4.7.1/

for QT4LOC I'm not sure.  I'm guessing that is where KDE has put the 
latest Qt 4/5?  Because

> libqt4-devel-4.7.1-154.1
> qt3-devel-3.3.8b-87.11
> qt3-3.3.8b-87.11

suggests to me you don't have Qt4 on your system.  Just the code for 
building the Qt4 library.

So, what you are proposing is that if the rcc for Qt4 does not exist at 
the expected location, configure just falls back on "rcc".  I suppose 
that is the best that can be hoped for.

What happens when you type "rcc" at a command line?  I'm using FC14 and get

[root@moorglade gnuplot]# rcc -version
Qt Resource Compiler version 4.7.4

so I know that my tools/resources are of the Qt4 variety.  I'm wondering 
if yours might not be.

Dan


>
> Petr
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>

-- 

Dan Sebald
email: daniel(DOT)sebald(AT)ieee(DOT)org
URL: http://www(DOT)dansebald(DOT)com