discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] coding entirely in C++


From: crjqq
Subject: Re: [Discuss-gnuradio] coding entirely in C++
Date: Fri, 26 Jun 2009 22:35:21 -0700 (PDT)

Thanks for the link. I'll study the file to learn more about writing GNU radio 
apps in c++.
I noticed that this was the only example in the c++ directory.
Any pointers on compiling the c++ source files? libraries, compiler options  
and such.

Thank you
-Rush

--- On Sat, 6/27/09, Philip Balister <address@hidden> wrote:

> From: Philip Balister <address@hidden>
> Subject: Re: [Discuss-gnuradio] coding entirely in C++
> To: "address@hidden Org" <address@hidden>
> Date: Saturday, June 27, 2009, 4:06 AM
> address@hidden
> wrote:
> > I want to write GNUradio apps entirely in C++.
> > 
> > Could anyone outline a general procedure of converting
> a sample python example(say, dial_tone.py) to c++?
> 
> Does this help?
> 
> http://gnuradio.org/trac/browser/gnuradio/trunk/gnuradio-examples/c%2B%2B/dial_tone/dial_tone.cc
> 
> Philip
> 
> > 
> > I saw online that the usrp can be interfaced by using
> the -lusrp switch when using g++. How do I find the
> corresponding -l... switches when I include the c++ headers
> I need?
> > 
> > Also, after building GNUradio 3.2, I could see pyhton
> examples in the folder
> gnuradio-3.2/gnuradio-examples/python/ but didn't find the
> c++ examples in gnuradio-3.2/gnuradio-examples/c++.
> > Did I forget a step while building or these examples
> don't exist?
> > 
> > Any help would be appreciated.
> > 
> > -Rush
> > 
> > 
> >       
> > 
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > 
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


      




reply via email to

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