Hello I have been fighting to compile the gr-osmosdr package in my osx
These are the minor fixes I had to do: 1- Change in Cmakelists.txt: find_package(Boost COMPONENTS thread system), If thread and system is not included then there are linking problems. Although I see that this was removed recently...
2- cmake -DCMAKE_INSTALL_PREFIX=/opt/local (so it is installed together wit my ports intallation, this is really optional) 3- Before compiling I manually edit CmakeCache.txt, and change all the references of /usr/lib/python to /opt/local/lib/python. If not it links agains the system python instead of the ports's python! 4- Add this line in my .bashrc so python can find the package export PYTHONPATH="/opt/local/lib/python2.7/site-packages/"
I am aware that this is not the most elegant way to solve the problem but is the only one that I was able to come up. Hope it helps
Regards
On Fri, Apr 26, 2013 at 8:40 PM, Alberto Albiol alalbiol@iteam.upv.es wrote:
Hello I have been fighting to compile the gr-osmosdr package in my osx
These are the minor fixes I had to do: 1- Change in Cmakelists.txt: find_package(Boost COMPONENTS thread system), If thread and system is not included then there are linking problems. Although I see that this was removed recently...
2- cmake -DCMAKE_INSTALL_PREFIX=/opt/local (so it is installed together wit my ports intallation, this is really optional) 3- Before compiling I manually edit CmakeCache.txt, and change all the references of /usr/lib/python to /opt/local/lib/python. If not it links agains the system python instead of the ports's python! 4- Add this line in my .bashrc so python can find the package export PYTHONPATH="/opt/local/lib/python2.7/site-packages/"
I am aware that this is not the most elegant way to solve the problem but is the only one that I was able to come up. Hope it helps
Hi Alberto,
Perhaps the gr-osmosdr package in macports can be of some help for how to compile without manually editing the build files: https://trac.macports.org/browser/trunk/dports/science/gr-osmosdr/Portfile
Alex
Hi,
Sorry for the rather abrupt email. I should have just waited 'til I got home.
I recently fixed the homebrew formula for gnuradio and gr-osmosdr, as well as the gr-osmosdr CMakeLists.txt.
They can be found here: https://github.com/mjmdavis/homebrew-gnuradio https://github.com/mjmdavis/gr-osmosdr
I had to implement the same fix as you did in the CMakeLists.txt. I'm not sure how people have been building it without that step. Hopefully the changes can be pulled back into the main repo.
To install using brew on mac is dead easy. Just have a look here: https://github.com/mjmdavis/homebrew-gnuradio
I will be updating the formula to reference the latest gnuradio sometime later today. There is currently a bug with the --with-qt option that I am looking into but in most cases the Qt stuff is not necessary.
This probably isn't much help for you if you already use macports though, I'm not a fan of having multiple package managers.
Best, Mike
On 1 May 2013, at 13:21, Alexandru Csete oz9aec@gmail.com wrote:
On Fri, Apr 26, 2013 at 8:40 PM, Alberto Albiol alalbiol@iteam.upv.es wrote:
Hello I have been fighting to compile the gr-osmosdr package in my osx
These are the minor fixes I had to do: 1- Change in Cmakelists.txt: find_package(Boost COMPONENTS thread system), If thread and system is not included then there are linking problems. Although I see that this was removed recently...
2- cmake -DCMAKE_INSTALL_PREFIX=/opt/local (so it is installed together wit my ports intallation, this is really optional) 3- Before compiling I manually edit CmakeCache.txt, and change all the references of /usr/lib/python to /opt/local/lib/python. If not it links agains the system python instead of the ports's python! 4- Add this line in my .bashrc so python can find the package export PYTHONPATH="/opt/local/lib/python2.7/site-packages/"
I am aware that this is not the most elegant way to solve the problem but is the only one that I was able to come up. Hope it helps
Hi Alberto,
Perhaps the gr-osmosdr package in macports can be of some help for how to compile without manually editing the build files: https://trac.macports.org/browser/trunk/dports/science/gr-osmosdr/Portfile
Alex
Thanks Alex for your reply. Actually in the time being it looks that all the dependencies in macports have been fixed and now gr-osmosdr can be complied without any issue!
One more thing for those installing gnu radio I found that this tricky option can be useful since the default compiler is clang: sudo port install gnuradio-devel +full configure.compiler=gcc
It seems that the use of gcc improves performance on vector operations......
Regards
On Wed, May 1, 2013 at 1:21 PM, Alexandru Csete oz9aec@gmail.com wrote:
On Fri, Apr 26, 2013 at 8:40 PM, Alberto Albiol alalbiol@iteam.upv.es wrote:
Hello I have been fighting to compile the gr-osmosdr package in my osx
These are the minor fixes I had to do: 1- Change in Cmakelists.txt: find_package(Boost COMPONENTS thread
system),
If thread and system is not included then there are linking problems. Although I see that this was removed recently...
2- cmake -DCMAKE_INSTALL_PREFIX=/opt/local (so it is installed together
wit
my ports intallation, this is really optional) 3- Before compiling I manually edit CmakeCache.txt, and change all the references of /usr/lib/python to /opt/local/lib/python. If not it links agains the system python instead of the ports's python! 4- Add this line in my .bashrc so python can find the package export PYTHONPATH="/opt/local/lib/python2.7/site-packages/"
I am aware that this is not the most elegant way to solve the problem
but is
the only one that I was able to come up. Hope it helps
Hi Alberto,
Perhaps the gr-osmosdr package in macports can be of some help for how to compile without manually editing the build files: https://trac.macports.org/browser/trunk/dports/science/gr-osmosdr/Portfile
Alex
-
Alberto Albiol -
Alexandru Csete -
Michael Davis