Please respond....

[Anne Ranch]

After few   days of no response , I realize I may be in wrong group. ...

I'll will try this . I manged to clone the current release and having a heck of a time compiling it.  I AM NOT ASKING FOR HELP CODING...,. I just like to know if CURRENT version SHOULD   COMPile .  Ir is complaining  of few undefined symbols  please do NOT  reply if YOU CONFIRM THIS , REPLY only if i CLONED  WRONG VERSION....

# Project name
project(gqrx)
set(${PROJECT_NAME}_MAJOR "2")
set(${PROJECT_NAME}_MINOR "17")
set(${PROJECT_NAME}_PATCH "7")
set(IS_RELEASE TRUE)

[David Ranch]

You haven't told us what repo you've cloned but it's important to understand that Gqrx a combination of many projects including GnuRadio, various SDR libraries like soapy, librtl, etc.  It's not clear what you're wanting to do or on what platform but if Linux, using the posted appimages at https://github.com/gqrx-sdr/gqrx/releases is by far the best and fastest way to get it running.  If you really want to compile everything from the ground up, are you following the guide at https://github.com/gqrx-sdr/gqrx/blob/master/README.md ?  If so, where do things break (please include the specific errors) so the group can give you specific answers.

--David

KI6ZHD

[Anne Ranch]

Thanks for your reply . My current goal is to have an editable .pro project in Qt. I have followed the "standard" Qt clone and cannot maKe it play. I have managed to "build" using commands and cannot figure out WHERE is my final "qgrex" SOURCE. ...

I am going to try  combining commands and Qt.... my next step. I have all "prerequisites" loaded....

For a specific question - I see  several, at least two versions of "....txt " file....I am currently "building" another  copy using commands... 

here is the tail of the progress messages ...no errors 

[ 97%] Building CXX object src/CMakeFiles/gqrx.dir/qrc_icons.cpp.o
[ 98%] Building CXX object src/CMakeFiles/gqrx.dir/qrc_textfiles.cpp.o
[100%] Linking CXX executable gqrx
[100%] Built target gqrx
sda@sda-desktop:~/gqrx.git.v3/build$

so --- how do I check / verify the resulting source code ?? Where is it ? Can Qt "see it " as what ??? I will be happy if it runs, but from where ??? Can you help ??

--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqrx+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gqrx/5a0d7219-3645-4531-ae44-20d1f4fea074n%40googlegroups.com.

[Anne Ranch]

sda@sda-desktop:~/gqrx.git.v3/build$ gqrx

this runs my installed / downloaded  gqrex NOT the one I just built.  I could  just delete it, but still need to know where is my last V3 build ...

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.1.1
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
file_source :warning: file size is not a multiple of item size
Resampling audio 96000 -> 48000
BandPlanFile is /home/sda/.config/gqrx/bandplan.csv
BookmarksFile is /home/sda/.config/gqrx/bookmarks.csv
[INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3
libusb: warning [libusb_exit] device 2.4 still referenced
libusb: warning [libusb_exit] device 2.3 still referenced
libusb: warning [libusb_exit] device 2.2 still referenced
libusb: warning [libusb_exit] device 2.1 still referenced
libusb: warning [libusb_exit] device 1.17 still referenced
libusb: warning [libusb_exit] device 1.16 still referenced
libusb: warning [libusb_exit] device 1.15 still referenced
libusb: warning [libusb_exit] device 1.14 still referenced
libusb: warning [libusb_exit] device 1.13 still referenced
libusb: warning [libusb_exit] device 1.5 still referenced
libusb: warning [libusb_exit] device 1.9 still referenced
libusb: warning [libusb_exit] device 1.6 still referenced
libusb: warning [libusb_exit] device 1.3 still referenced
libusb: warning [libusb_exit] device 1.2 still referenced
libusb: warning [libusb_exit] device 1.1 still referenced
Detached kernel driver
Found Rafael Micro R820T tuner
Reattached kernel driver
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.1.1
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
[INFO] Using format CF32.
sda@sda-desktop:~/gqrx.git.v3/build$

[Anne Ranch]

SUCCESS  

now compiled in Qt 

[80/82 0.4/sec] Building CXX object src/CMakeFiles/gqrx.dir/pulseaudio/pa_source.cc.o

[81/82 0.4/sec] Building CXX object src/CMakeFiles/gqrx.dir/receivers/wfmrx.cpp.o
[82/82 0.4/sec] Linking CXX executable src/gqrx
10:14:39: The process "/home/sda/Qt_sda/Tools/CMake/bin/cmake" exited normally.
10:14:39: Elapsed time: 03:23.

[David Ranch]

It looks like gqrx completed it's build so that's very good.  Did you also build a new version of GnuRadio too?  I ask because I know that Gqrx only works 100% with specific versions of GnuRadio, some of the libraries, etc.  Again, it's a complex matrix of code to get things working which is all factored into the Linux AppImage and Apple DMGs.    Anyway, try this where you *must* include the "./" to tell Linux to run the binary in the LOCAL directory and not binaries in your PATH.

   cd ~/gqrx.git.v3/build

   ./gqrx

--David

KI6ZHD

[Anne Ranch]

I should say  that  this is my FIRST code using "make" , and its derivatives. My other code is all Qt .pro based and it will take some experimenting to "tune" make. I'll say it again - I was after "compile" and so far my original "make" actually runs. I found adding "make project" is similar to adding  .pro, however removing it escapes me... BTW it takes about 3 minutes for FULL compile. Maybe I need to change my terminology to "make" instead  of "compile" ... ( I did find the option to speed "make " . do only recent change ) But Qt uses "build " or "rebuld"....or "Run CMake"....  too many choices  HI HI 

To view this discussion visit https://groups.google.com/d/msgid/gqrx/4459d163-60d5-46ec-8721-831d1cf6b1b8n%40googlegroups.com.

[Andrea Lawendel]

Hi, 

In the past I've tried to compile with QT the Inmarsat decoding software Jaero, with no success at all! :-)

It's not clear wether you now have an executable Gqrx binary or not. Are you doing this to sharpen your QT knowledge, or your goal is being able to run Gqrx on you rmachine? In MacOS the easiest solution by far is a Homebrew install (after installing GNU Radio with the same packet manager e compiling/brewing other dependencies) or a compile with Cmake. 

For both, there was some problems related to a dynamic link which prevents one of the latest version of Gqrx from launching correctly.

Andy

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CAMawYRnm5agJNDbWOv5ypu0yZf0bO8nkJc50pbEczYDGUBWEBg%40mail.gmail.com.

[Bruce]

QT Creator uses make/cmake under the hood.

If you want to modify and debug the code, an integrated development environment (IDE), like Creator, is easier.

If you just want to compile existing code, using an IDE is probably overkill.

I use QT Creator for GQRX as I'm running a fairly modified version.

The resultant binary ends up in a subdirectory named after the target system, and there are different locations for debug Vs run versions.

You don't have to use QT Creator to compile code written in QT language (eg. GQRX), and Creator can compile code that doesn't use QT.

Cheers,
Bruce

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CAKRhKPWZJpP2dFAM3ifivBZURfuJWVRvRTKvB-tmPJ7LHW0VEw%40mail.gmail.com.

[Andrea Lawendel]

Thank you, Bruce. My developing skills are quite limited and your notes help me getting a clearer picture! But how compilation of Gqrx’s many dependencies, including , would fit in the IDE approach? I understand I could for example use Homebrew to have GNUradio and other “pieces” installed separately while switching to Creator when it comes to Gqrx code, but would it be possible to have Creator compile one or more dependencies as well? Even those for which there’s no a specific project (.pro) file?

Please forgive me if I’m going slightly off topic with this…

Andy

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CAGqxWvJ38HoqEd1R4Z46NVAqd0abzXt6DXi%3DVfC4NSLARViM2w%40mail.gmail.com.

[Bruce]

I honestly can't recall how I got it all to go under QT Creator. It's a while ago. Maybe there was a simple way to take the Cmake file provided and create a .pro file from it?

You don't have to compile everything yourself either. 

Gnuradio, for instance, is a library you can include - it could have been complied from source separately (another directory tree), or comes from a package installation. All you will need is the include files to reference the library calls, and there are dev packages specially for that purpose.

I also recall compiling soapy, to include some bits for attenuation control that were #defined out in the standard release.

Cheers,
Bruce

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CAKRhKPWnJ78tSryAfPvaMXdoQ9sr%2B0QQG-j6TbGnotHD7r5H-A%40mail.gmail.com.

[Anne Ranch]

I am making progress learning CMake... I have a working copy of gqex , however I suspect my hardware is not working,,,,

I have several "open source" copies of code and am currently learning  how to add it as an "existing project" into  my own base app. 

My coding philosophy is - "if you do not need it , hide it" so I am rebuilding the original using QMDIArea ( heavy on menus ) and I got the base working... My next objective is to add "waterfall scanner ", I can "pounce and search" to find where the BASE waterfall code resides  but if somebody can give me a hint  it would help ..

To view this discussion visit https://groups.google.com/d/msgid/gqrx/CAGqxWvJbjruHwE_KRJOGnB_Gv6xRjr6z%3DeFFZ86AtUF2aaCu8g%40mail.gmail.com.

[Donkiss Boss]

Licensed Pharmaceuticals And Psychedelics Online Store
Buy the best Pharmaceuticals And Psychedelics products in our website with safe and guaranteed shipping and delivery Worldwide
Check out our website below if interested in our products.
https://shorturl.at/BvDVf
https://shorturl.at/ITBJW
https://shorturl.at/wCGS4
https://shorturl.at/RnP0b
https://shorturl.at/GTr8Q