PyBOMBS and apt-get'd GNU Radio playing nicely about pybombs HOT 5 CLOSED

The only problem is that the gnuradio recipe doesnt have a "satisfy_deb:"
statement, so pybombs won't check to see if the gnuradio deb is installed.
Adding "satisfy_deb: gnuradio" to the gnuradio recipe should fix this
problem. I'm assuming the deb is called gnuradio, but maybe should be
gnuradio-dev. I'm not in a spot right now to check/fix this but will check
it out later.

Tim

On Mon, Jun 23, 2014 at 10:24 AM, Tom Rondeau [email protected]
wrote:

I don't have the full work-flow to re-do this problem, but it's been
reported to me over email. It seems like doing an "apt-get install
gnuradio" and then using PyBOMBS to install an OOT project causes PyBOMBS
to rebuild it's own version of GNU Radio and therefore putting multiple
versions of GR into the system.

My guess is that this wouldn't be a problem when using 'apt-get install
gnuradio-dev' since building the OOT projects requires the headers and dev
version of GNU Radio.

Can we check for an installed GNU Radio library as well as the header
files? If the libraries are found but the headers aren't, PyBOMBS should
exit with a warning about not having the dev version of GNU Radio installed
instead of just building and installing a new version.

—
Reply to this email directly or view it on GitHub
#80.

from pybombs.

Do we really want to support binary gnuradio pybombs configurations?

from pybombs.

yes

On Tuesday, June 24, 2014, osh [email protected] wrote:

Do we really want to support binary gnuradio pybombs configurations?

—
Reply to this email directly or view it on GitHub
#80 (comment).

Johnathan Corgan
Corgan Labs - SDR Training and Development Services
http://corganlabs.com

from pybombs.

Yes, we do. We're trying to push more people to use apt-get and yum for the installation process of GNU Radio on those systems. We want to focus PyBOMBS here to be the way to easily install OOT projects, and we don't want this to lead to the problem of having 2 versions of GNU Radio installed in /usr and whatever PyBOMBS prefix.

from pybombs.

We may need a few different pybombs recipe sets to allow users to choose their "danger level"

• if possible I would kind of like a single set of recipes to define a specific one of these instead of allowing any of them. But perhaps the initial environment setup can help the user get on the right recipe set / pybombs git branch for their interests.
  1. ubuntu binary based gnuradio
  2. pybombs gnruadio maint git based build
  3. pybombs gnuradio master git based source build

from pybombs.