Opened 15 years ago

Last modified 14 years ago

#18104 closed submission

GnuRadio on Macports — at Version 10

Reported by: g-h-o-s-t-l-a-b Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.7.0
Keywords: Cc: snc@…, mlk@…, devans@…
Port: gnuradio

Description (last modified by dbevans (David B. Evans))

# $gnuradio$

PortSystem          1.7.0 # ?

name                gnuradio
version             3.1.3
categories          # ? /SDR software defined radio?
maintainers         # ?
description         software defined radio
long_description    GNU Radio is a free software development toolkit that provides the signal processing runtime and processing blocks to implement software radios using readily-available, low-cost external RF hardware and commodity processors. It is widely used in hobbyist, academic and commercial environments to support wireless communications research as well as to implement real-world radio systems.
GNU Radio applications are primarily written using the Python programming language, while the supplied, performance-critical signal processing path is implemented in C++ using processor floating point extensions where available. Thus, the developer is able to implement real-time, high-throughput radio systems in a simple-to-use, rapid-application-development environment.
While not primarily a simulation tool, GNU Radio does support development of signal processing algorithms using pre-recorded or generated data, avoiding the need for actual RF hardware.
homepage            http://gnuradio.org/trac
platforms           darwin
master_sites        http://www.gnu.org/software/gnuradio/                    

checksums           # ? 
                               # ? 
depends_lib         port:libtool \
                    port:gawk \
                    port:guile \
                    port:pkgconfig \
                    port:zlib \
                    port:automake \
                    port:swig \
                    port:cppunit \
                    port:fftw-3-single \
                    port:sdcc \
                    port:python \
                    port:py-numpy \
                    port:py-wxpython \
                    port:doxygen \
                    port:boost \
                    port:libusb

configure.args     # Maybe "--with-boost-include-dir=<path>"
                  

Change History (15)

Changed 15 years ago by g-h-o-s-t-l-a-b

Attachment: GnuRadio_port.2.rtf added

Changed 15 years ago by g-h-o-s-t-l-a-b

Attachment: GnuRadio_port.rtf added

uploaded file

Changed 15 years ago by g-h-o-s-t-l-a-b

Attachment: GnuRadio-port.txt added

Changed 15 years ago by g-h-o-s-t-l-a-b

Attachment: GnuRadio-port.2.txt added

comment:1 Changed 15 years ago by nerdling (Jeremy Lavergne)

If you've not had a chance, please see http://guide.macports.org/#development

Please see some suggested modifications in my attached Portfile.

Changed 15 years ago by nerdling (Jeremy Lavergne)

Attachment: Portfile added

comment:2 Changed 15 years ago by nerdling (Jeremy Lavergne)

Cc: snc@… added

Cc Me!

comment:3 Changed 15 years ago by michaelld (Michael Dickens)

Cc: mlk@… added

Cc Me!

comment:4 Changed 15 years ago by michaelld (Michael Dickens)

I'm a GNU Radio developer, so feel free to ask me questions if you need answers. - MLD

Some items to note:

  • GNU Radio 3.2 is about to be released. I highly recommend waiting until then to create ports for it. 3.1.3 has a lot of limitations and issues that are fixed in 3.2, and the API for most features will be stable (wasn't for 3.1.3).
  • GNU Radio 3.1.3 can use Python 2.4 or 2.5, while 3.2 requires Python 2.5. GNU Radio does not work with Python 2.6 yet, but will in the near future; either way, MacPorts does not provide the correct py26-foo ports yet, so work remains on both sides for this advancement.
  • "--with-boost-include-dir" might be used, or set CPATH in configure.env correctly (to ${prefix}/include ). This should be sussed out before submitting the Portfile.
  • "--enable-all-components" is not required, and I'd recommend against using it because configure will then error out if -any- non-disabled component can't be built. Not specifying it will just not build that/those component/s, instead of erroring out.
  • "gr-audio-jack" and "gr-audio-portaudio" should be optional components, since they can be compiled and used on OSX. Although they do require "jack" and "portaudio" ports, respectively, they should work "out of the box" when the user select either of those instead of the "gr-audio-osx" native audio I/O component.
  • There are a number of components to GNU Radio which a user may or not want (e.g., grc, gr-audio-osx, gr-gsm-vocoder). Under Linux, one can install just gnuradio-core (and its dependencies) or all the way up to a "gnuradio" meta-port. See the "gimp" meta-port in MacPorts for an example of how GNU Radio components should be available.
  • I'll submit the host of Portfiles for individual components which can work on OSX (except gr-qtgui) once 3.2 is released. The should work "out of the box" for any 10.4 or 10.5 OSX MacPorts user. I've got them working with the latest SVN trunk, which is 3.2rc1, on OSX 10.5. I expect them to work with the actual 3.2 release, but there could be minor changes between then and now which require tweaks to the Portfiles -- which is why I'm not releasing them until 3.2 is released.

comment:5 Changed 15 years ago by g-h-o-s-t-l-a-b

Cc: horiacosmin@… added

Cc Me!

comment:6 Changed 15 years ago by g-h-o-s-t-l-a-b

Cc: horiacosmin@… removed

Cc Me!

comment:7 Changed 15 years ago by g-h-o-s-t-l-a-b

Cc: horiacosmin@… added

Cc Me!

comment:8 Changed 15 years ago by g-h-o-s-t-l-a-b

Great! how could we contact together?

comment:9 Changed 15 years ago by g-h-o-s-t-l-a-b

Sorry, havn't saw the e-mail adress...

comment:10 Changed 15 years ago by dbevans (David B. Evans)

Cc: devans@… added; horiacosmin@… removed
Description: modified (diff)

Please don't forget to use wiki formatting. Removing reporter from cc since he will be automatically copied.

Note: See TracTickets for help on using tickets.