make: Entering directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
/usr/bin/qmake -spec /usr/lib/qt4/mkspecs/linux-g++ -o Makefile ../csete-gqrx-a613fed/gqrx.pro
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Project ERROR: Package gnuradio-osmosdr not found
make: Leaving directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
make: *** [Makefile] Error 2
14:21:36: The process "/usr/bin/make" exited with code 2.
Error while building project gqrx (target: Desktop)
When executing build step 'Make'
Ok, if you chose to install to /usr/local/src then fine. It should
work without any changes to the source code or build files. I myself
have all gnuradio related stuff installed in various directories under
/opt/ and it works well (even multiple versions at the same time).
Qt -creator itself doesn't care about where gnuradio or gr-osmosdr is
installed. It uses pkg-config to find the libraries and headers. Thus
pkg-config must be told where to find these.
If you type "pkg-config --cflags --libs gnuradio-osmosdr" in a
terminal (without the quotes) what do you get?
make: Entering directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
/usr/bin/qmake -spec /usr/lib/qt4/mkspecs/linux-g++ -o Makefile ../csete-gqrx-a613fed/gqrx.pro
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Project ERROR: Package gnuradio-osmosdr not found
make: Leaving directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
make: *** [Makefile] Error 2
15:02:50: The process "/usr/bin/make" exited with code 2.
On Monday, July 30, 2012 8:07:43 PM UTC+10, Alexandru Csete wrote:Ok, if you chose to install to /usr/local/src then fine. It should
work without any changes to the source code or build files. I myself
have all gnuradio related stuff installed in various directories under
/opt/ and it works well (even multiple versions at the same time).
Qt -creator itself doesn't care about where gnuradio or gr-osmosdr is
installed. It uses pkg-config to find the libraries and headers. Thus
pkg-config must be told where to find these.
If you type "pkg-config --cflags --libs gnuradio-osmosdr" in a
terminal (without the quotes) what do you get?
I've made some progress, I now get the following:
[root@localhost build (master)]# pkg-config --cflags --libs gnuradio-osmosdr-I/usr/local/include/osmosdr -I/usr/local/include/gnuradio -I/usr/local/include -L/usr/local/lib -lgnuradio-osmosdr -lgnuradio-core -lgruel -lfftw3f -lm
But gqrx qt creator still cannot find gnuradio-osmosdr and I still get "not a git repository" fatal error.
make: Entering directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
/usr/bin/qmake -spec /usr/lib/qt4/mkspecs/linux-g++ -o Makefile ../csete-gqrx-a613fed/gqrx.pro
fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Project ERROR: Package gnuradio-osmosdr not found
make: Leaving directory `/home/phil/Download/qrx/gqrx-build-desktop-Qt_in_PATH_Release'
make: *** [Makefile] Error 2
15:02:50: The process "/usr/bin/make" exited with code 2.
Error while building project gqrx (target: Desktop)
When executing build step 'Make'
Do you have any particular reason for running the command as root instead of a regular user?
Please try it using the same user name as you use when running Qt Creator.
/usr/local/ has always been a directory that needs root permission to access and I've been in the habit, for the past 15 years, of becoming root whenever I need to do anything within the directory. I suppose old habits die hard. Anyway, the result is the same.
Sorry, I really have no clue about the git error. It is an error reported by git and I have no idea why git is involved in the build process? Did you by accident configure Qt creator to do some git stuff before building?
Of course, I assume that you are working inside Qt Creator and not trying to use qmake etc. from the command line.
Does it make any difference if you start Qtcreator from the terminal, i.e. "qtcreator gqrx.pro" (without the quotes).
You can try to remove the csete-gqrx-a613fed directory and also the gqrx-build-desktop-Qt_in_PATH_Release and make a fresh checkout using git:
git clone git://github.com/csete/gqrx.git gqrx.git
then cd to gqrx.git and load the gqrx.pro file using "qtcreator gqrx.pro"
Phil
That's good news Phil, but do you know why it works?
Alex
a) /usr/local/bin, orHowever, the defaults in the make script will usually put software in /usr/bin, which is generally acceptable, but trickier when it comes to removing, rather than installing, software. (The choice of where to put any software should be guided by the contents of the $PATH variable—echo $PATH will remind one what it currently is.)
b) /opt
--
You received this message because you are subscribed to the Google Groups "Gqrx SDR" group.
To post to this group, send email to gq...@googlegroups.com.
To unsubscribe from this group, send email to gqrx+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/gqrx/-/avztAwmStH8J.
On Sunday, August 5, 2012 6:05:21 AM UTC+10, Alexandru Csete wrote:That's good news Phil, but do you know why it works?
Alex
Yes, and it's somewhat embarrassing to have to admit. I thought about what you said earlier and realised that I had set the package config path is my bash.rc file but was trying to build the code as root. A lesson learned and perhaps I should change the permission of /usr/local to allow a normal user to have write access?
Gqrx is an amazing piece of work. I wonder if you're going to continue work on the project?