discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX


From: Johnathan Corgan
Subject: Re: [Discuss-gnuradio] gr_modtool cmake/make problems on OSX
Date: Mon, 25 Feb 2013 13:37:52 -0800

On Mon, Feb 25, 2013 at 12:40 PM, Warren, Kevin M <address@hidden> wrote:
 
Greetings all, this is my first post here so I apologize ahead of time for any clumsiness in the order and detail of my question. I'm using a Macport install of Gnuradio 3.6.3 (system particulars below). So far I've had a good deal of success with Gnuradio but I'm at the point where I need to start constructing custom modules. Unfortunately, I've encountered some difficulties with the out-of-tree build tutorial using gr_modtool. 

The gr_modtool has been integrated into the GNU Radio master branch post-3.6.3, and will be part of the 3.6.4 release.  At least one of the issues below has already been fixed.
 
1) A minor difficulty is that gr_modtool.py does not appear to be placing the class definitions and the instantiation of the class object(s) in the proper order. This was easy enough to remedy by hand. 

This has been fixed.

2) A second minor difficulty is that makexml does not appear to work at all. Again, this is easy enough to remedy by hand.

I'll let Martin Braun address this.
 
- My main problem that I'm 8+ hours into is that with my installation I cannot get cmake to set an explicit path to my dylib file and changing DYLD_LIBRARY_PATH produces other conflicts with gnuradio-companion.
 
Michael Dickens is our go-to guy for MacOSX issues; hopefully he can respond to this.

Using:
gr_modtool.py from github

As I mentioned, this has now become a standard feature of GNU Radio.  We should be releasing 3.6.4 very shortly; this will (eventually) make it into MacPorts.

Finally--I wanted to specifically thank you for the detailed bug report and a list of all the steps you have already taken to try to fix the issue.  It really helps us to 1) understand your problem, 2) rule out things you've already tried, and 3) helps others searching the mailing list archives trying to debug similar issues.

Johnathan

reply via email to

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