Request to add openSUSE 12.1 support to the build-gnuradio script

I’ve just corresponded with Marcus L. about adding support for
openSUSE
12.1 in the build-gnuradio script, and he’s said

“The cmake hackery might be better placed in the Cmake rules in Gnu
Radio itself–using yet-another special recognizer for OpenSuse. I
suggest
you post to discuss-gnuradio to indicate that OpenSuse requires this
rule,
and perhaps someone (maybe Josh) will patch the Cmake rules
appropriately.”

the place to check for openSUSE 12.1 is /etc/os-release and it
contains:
NAME=opensuse
VERSION = 12.1 (Asparagus)
VERSION_ID=“12.1”
PRETTY_NAME=“openSUSE 12.1 (Asparagus) (i586)”
ID=opensuse

i used the existing build-gnuradio script as an outline for building it
manually. the individual steps were quite successful.

here’s the key info:

sudo zypper install cmake cppunit-devel doxygen fftw3-devel git
gsl-devel
libjack-devel libqt4-devel libqwtplot3d-devel libSDL-devel
libusb-1_0-devel
orc portaudio portaudio-devel python-cheetah python-devel python-lxml
python-wxGTK python-wxWidgets-devel qwt-devel wxWidgets-devel xmlto

(add texlive-latex to the list above if you want all the gnuradio docs
to
build - latex install alone needs about 300MB of disk)

To enable building *gr-qtgui *in addition to all the rest, you have to
point cmake to the location of the qwt header files:
cmake -DQWT_INCLUDE_DIRS=/usr/include/qwt5 …/

On 04 Sep 2012 09:13, KB3CS - Chris wrote:

I’ve just
corresponded with Marcus L. about adding support for openSUSE 12.1 in
the build-gnuradio script, and he’s said

“The cmake hackery might
be better placed in the Cmake rules in Gnu Radio itself–using
yet-another special recognizer for OpenSuse. I suggest you post to
discuss-gnuradio to indicate that OpenSuse requires this rule, and
perhaps someone (maybe Josh) will patch the Cmake rules
appropriately.”

the place to check for openSUSE 12.1 is
/etc/os-release and it contains:
NAME=opensuse
VERSION = 12.1
(Asparagus)
VERSION_ID=“12.1”
PRETTY_NAME=“openSUSE 12.1 (Asparagus)
(i586)”
ID=opensuse

i used the existing build-gnuradio script as
an outline for building it manually. the individual steps were quite
successful.

here’s the key info:

sudo zypper install cmake
cppunit-devel doxygen fftw3-devel git gsl-devel libjack-devel
libqt4-devel libqwtplot3d-devel libSDL-devel libusb-1_0-devel orc
portaudio portaudio-devel python-cheetah python-devel python-lxml
python-wxGTK python-wxWidgets-devel qwt-devel wxWidgets-devel xmlto

(add texlive-latex to the list above if you want all the gnuradio
docs to build - latex install alone needs about 300MB of disk)

To
enable building GR-QTGUI in addition to all the rest, you have to point
cmake to the location of the qwt header files: cmake
-DQWT_INCLUDE_DIRS=/usr/include/qwt5 …/

To be clear, it’s only the
cmake stuff that I’d prefer be handled in the Gnu Radio build process
itself, rather than build-gnuradio special-casing it. We’ve done
distribution-specific “spooge” in the Cmake files a few times, and it
seems like this might be another instance of that.

The pre-requisite
support using zypper is no problem, and I already put that in that last.
But I’m waiting on opinions about the cmake flags – whether that should
be something in the gnuradio cmake files, or whether I need to
special-case it in build-gnuradio. Doing it in Gnu Radio itself means
that people doing manual builds will have a seamless experience.

On Tue, Sep 4, 2012 at 9:13 AM, KB3CS - Chris [email protected] wrote:

I’ve just corresponded with Marcus L. about adding support for openSUSE
12.1 in the build-gnuradio script, and he’s said

“The cmake hackery might be better placed in the Cmake rules in Gnu Radio
itself–using yet-another special recognizer for OpenSuse. I suggest you
post to discuss-gnuradio to indicate that OpenSuse requires this rule, and
perhaps someone (maybe Josh) will patch the Cmake rules appropriately.”

Hi Chris,

I’m not sure I understand what rule has to be added/changed for you?
Is it just the location of the QWT header files? That’s going to be a
continuous problem since they don’t produce a package config file for
us to work off of. We’re basically left to chase down all possible
include directories where we know it exists. Also, now that QWT 6 is
out, a lot of platforms are switching to that, so if we hard code
/usr/include/qwt5, that’ll just break when OpenSUSE moves to Qwt6 and
we’ll have to write another rule.

Any advice for how to best handle this situation is appreciated. (But
getting rid of Qwt isn’t an option; it’s way too useful.)

Tom

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs