#18104: GnuRadio on Macports -------------------------------------+-------------------------------------- Reporter: horiacosmin@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Submissions Component: ports | Version: 1.7.0 Keywords: | Port: -------------------------------------+-------------------------------------- Comment(by mlk@…): 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. -- Ticket URL: <http://trac.macports.org/ticket/18104#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS