Opened 11 years ago

Closed 11 years ago

#37076 closed defect (fixed)

gnuradio: gr-qtgui - can't find Qt4 during build process

Reported by: sebastian.herzberg@… Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: gnuradio-qtgui

Description

Hi,

at first I would like to thank you for the new gnuradio version.

I am having some trouble getting the qtgui (mainly gnuradio-companion) to build. It seems that during the config process cmake is not able to find Qt4 on my machine. So I tried another installation on a completely new and clean Mac OS 10.8.2 but got the same problem.

-- Could NOT find Qt4 (missing:  QT_QMAKE_EXECUTABLE QT_MOC_EXECUTABLE QT_RCC_EXECUTABLE QT_INCLUDE_DIR QT_LIBRARY_DIR QT_QTCORE_INCLUDE_DIR QT_QTCORE_LIBRARY QT_QTGUI_INCLUDE_DIR QT_QTGUI_LIBRARY QT_UIC_EXECUTABLE) (Required is at least version "4.2.0")
-- Found Qwt: /opt/local/lib/libqwt.dylib  
-- 
-- Python checking for PyQt4
-- Python checking for PyQt4 - found
-- 
-- Configuring gr-qtgui support...
--   Dependency Boost_FOUND = TRUE
--   Dependency QT4_FOUND = FALSE
--   Dependency QWT_FOUND = TRUE
--   Dependency ENABLE_GR_CORE = ON
--   Dependency PYTHONLIBS_FOUND = TRUE
--   Dependency PYQT4_FOUND = TRUE
--   Disabling gr-qtgui support.
--   Override with -DENABLE_GR_QTGUI=ON/OFF

All the Qt binarys are available (qt4-mac @4.8.3_1+quartz (active)) at /opt/local/bin which is also the first entry in $PATH.

Is there any way to point the configuration to look into /opt/local/bin or set the variables manually via ccmake?

System is a MBP, Mac OS 10.8.2, Python 2.7.3 via MacPorts 2.1.2

Attachments (2)

main.log (1012.8 KB) - added by sebastian.herzberg@… 11 years ago.
gr-qtgui-conf-out.txt (133.5 KB) - added by sebastian.herzberg@… 11 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 11 years ago by mf2k (Frank Schima)

Keywords: gnuradio Qt4 removed
Owner: changed from macports-tickets@… to michaelld@…
Port: gnuradio-qtgui added; gnuradio removed

In the future, please fill in the Port field with the port that failed to build and Cc the port maintainer(s).

comment:2 Changed 11 years ago by michaelld (Michael Dickens)

The new GNU Radio ports use the variant "+qtgui" to enable the use of Qt in this way. To replicate the old gnuradio port, you'd use "sudo port install gnuradio +full +python27" for example if you want to use Python 2.7. If the "+qtgui" variant is not set, then Qt4 will not be required and you will see what you saw. That said, it's certainly possible that CMake isn't finding the installed Qt4 for some reason. If using the variant doesn't work, then please do:

sudo port clean gnuradio
sudo port -d configure gnuradio +qtgui [+ other variants] > ~/Desktop/gr-qtgui-conf-out.txt 2>&1

and then post the output file to this ticket.

Changed 11 years ago by sebastian.herzberg@…

Attachment: main.log added

Changed 11 years ago by sebastian.herzberg@…

Attachment: gr-qtgui-conf-out.txt added

comment:3 Changed 11 years ago by sebastian.herzberg@…

Config works fine now, I just didn't get the syntax

Build fails, see main.log

comment:4 Changed 11 years ago by michaelld (Michael Dickens)

What is the actual "port" command line you're using? I can work out most, maybe all, of the variants from the files, but it's more reliable to ask.

comment:5 Changed 11 years ago by sebastian.herzberg@…

sudo port install gnuradio +qtgui +grc +uhd +wavelet +orc +swig +python27
Last edited 11 years ago by sebastian.herzberg@… (previous) (diff)

comment:6 Changed 11 years ago by sebastian.herzberg@…

Ok, I gave it another try because I needed grc working today. I uninstalled and cleaned the complete MacPorts installation and used the above command to install everything from the ground up. It took about 90 minutes to complete and so far it seems to be working fine. Thanks for your support anyway :)

Request for ticket to be closed.

comment:7 Changed 11 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

OK; thanks for reporting back.

Note: See TracTickets for help on using tickets.