discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] MacPorts and out-of-tree modules


From: Péter Horváth
Subject: [Discuss-gnuradio] MacPorts and out-of-tree modules
Date: Fri, 26 Jul 2013 18:50:11 -0500

Hi,

I try to use my out-of-tree modules using OS X 10.8 and the MacPorts version of gnuradio. I'm not very experienced with OS X. Gnuradio itself works well when installed using MacPorts.

I configure the out-of-tree modules with
DGR_PYTHON_DIR=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages 
DCMAKE_INSTALL_PREFIX=/opt/local

(after having patched GrPython.cmake so that it indeed handles GR_PYTHON_DIR)

So, the Python stuff ends up in this esoteric site-packages folder instead of /opt/local/lib/..., exactly as core the gnuradio modules do, and the .dylib file goes to /opt/local/lib, where the core gnuradio stuff seems to reside as well. However, although I can import the swig'd Python modules, the .dylib is not found. Core gnuradio stuff works. What am I missing here?

On a side note, how do you configure gnuradio itself if you want to compile it yourself instead of getting it from the macports distribution? Are those two options above correct and sufficient? 

I've got gcc-4.7 from macports, but still the macports-gnuradio gets compiled with CLANG. Is that normal? :) 
Best,
Peter


reply via email to

[Prev in Thread] Current Thread [Next in Thread]