Re: [Discuss-gnuradio] On config.h (was Check for gr-ctrlport)
Hi,
Does anyone else have strong opinions on this subject? Or will the
path to using the gnuradio/header.h model be enough?
Personally I think that gnuradio/header.h is the right way to go. Of
course that also mean that the pkg-config .pc must have
-I${PREFIX}/include rather than -I${PREFIX}/include/gnuradio or else
that defeats the point.
But the problem I see is that 3.7 is not there yet and as of now, the
config.h is broken and that should be fixed ... it has also caused
issue in some osmocom code because of name conflicts.
If in 3.7 we're going to have to change include gr_xxx.h to include
gnuradio/xxx.h anyway, then using gr_config.h now seems appropriate.
Cheers,
Sylvain
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] macport switching between gnuradio and gnuradio-devel ports with installed gr-osmosdr?
Mike, I wanted to switch from gnuradio macport to gnu radio-devel port to hopefully avoid the following error: bash-3.2$ ./multimode.py Mac OS; GNU C++ version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00); Boost_105300; UHD_003.005.001-0-unknown Using Volk machine: sse4_1_64_orc Traceback (most recent call last): File ./multimode.py, line 1086, in module tb = multimode(ahw=options.ahw, ppm=options.ppm, vol=options.vol, ftune=options.ftune, xftune=options.xftune, srate=options.srate, upclo=options.upclo, devinfo=options.devinfo, agc=options.agc, arate=options.arate, upce=options.upce, mthresh=options.mthresh, flist=options.flist, mbw=options.mbw, deemph=options.deemph, dmode=options.dmode, dfifo=options.dfifo, aout=options.aout, freq=options.freq) File ./multimode.py, line 301, in __init__ self.wxgui_waterfallsink2_0.set_callback(wxgui_waterfallsink2_0_callback) File /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gnuradio/gr/hier_block2.py, line 54, in __getattr__ return getattr(self._hb, name) AttributeError: 'gr_hier_block2_sptr' object has no attribute 'set_callback' bash-3.2$ I had the following installed: bash-3.2$ port installed gnuradio The following ports are currently installed: gnuradio @3.6.4.1_0+docs+full+grc+jack+orc+portaudio+python27+qtgui+sdl+swig+uhd+wavelet+wxgui (active) bash-3.2$ bash-3.2$ port installed rtl-sdr The following ports are currently installed: rtl-sdr @20130301_0 (active) bash-3.2$ bash-3.2$ port installed gr-osmosdr The following ports are currently installed: gr-osmosdr @20130313_0+docs+full+python27+swig+uhd (active) bash-3.2$ I deactivated gnuradio, and installed and activated gnuradio-devel. However this will not work with gr-osmosdr port since it is dependent on 'gnuradio', see (I assume there is an issue with not being able to be dependent on two other ports in an 'or' relationship?): bash-3.2$ port deps gr-osmosdr Full Name: gr-osmosdr @20130313_0+python27 Fetch Dependencies: git-core Build Dependencies: cmake Library Dependencies: gnuradio, rtl-sdr, python27 bash-3.2$ Any suggestions? Thanks, mlk PS: Thanks for adding the gr-osmosdr package to macports. Hopefully there is a simple way to install it so that it can work with either gnuradio or gnuradio-devel when switching back and forth. I suppose another way to do this might be to not install macports gr-osmosdr and instead install their package in /user/local so that either gnuradio or gnuradio-devel could use it without the dependency issue. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Source block for the funcube pro plus
On Thu, Mar 28, 2013 at 11:41 AM, Volker Schroer dl1...@gmx.de wrote: Just for your information: In imitation of the gr-fcd source I set up a gnuradio source for the funcube pro+ ( linux only) . To avoid the crashes depending on libusb I used the hidraw driver. The source and an example can be found on https://github.com/dl1ksv/gr-fcdproplus.git Comments are welcome. Enjoy it Hi Volker, Nice work. I would recommend letting the user specify the device string and only use auto-detection if string is empty. Alex ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Radio frequency range description list?
Hi, Has anyone created a machine parsable file that lists radio frequencies and what is covered by that range? At the simplest level I am thinking of something that would include country code, a frequency range and the identifier to what that range is, and possibly a string indicating typical data encoding. The idea being when using a UI, such as Gqrx you would be able to have a label identifying what sort of data you should be seeing and in other cases use this information for automatically loading the right configuration(s) for handling that frequency range. Andre ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] pktno ??!!
I suppose you can do something similar to this n = 0 data = file.read(pkt_size) while data != : make payload send payload n += 1 print n On Fri, Mar 29, 2013 at 11:29 PM, manjusha yandamuri.ma...@gmail.comwrote: is there no way to do it??!!any other ideas on how can it be implemented?! - Manjusha -- View this message in context: http://gnuradio.4.n7.nabble.com/pktno-tp40416p40426.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- Manu T S ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] pktno ??!!
Sorry, I missed a line. you should have a data = file.read(pkt_size) inside the while loop as well. On Mon, Apr 1, 2013 at 7:53 AM, Manu T S manu.t.s...@gmail.com wrote: I suppose you can do something similar to this n = 0 data = file.read(pkt_size) while data != : make payload send payload n += 1 print n On Fri, Mar 29, 2013 at 11:29 PM, manjusha yandamuri.ma...@gmail.comwrote: is there no way to do it??!!any other ideas on how can it be implemented?! - Manjusha -- View this message in context: http://gnuradio.4.n7.nabble.com/pktno-tp40416p40426.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- Manu T S -- Manu T S ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
