discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Problem with gnuradio-companion


From: Marcus Müller
Subject: Re: [Discuss-gnuradio] Problem with gnuradio-companion
Date: Wed, 3 Aug 2016 21:37:28 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0

Hi Mike,

On 08/03/2016 09:29 PM, Mike Willis wrote:

Well I did work it out eventually, it is extremely difficult for non-expert developers to use this software to anything like its potential.

Honestly, I can feel your frustration, believe me. I'd love being able to roll out GNU Radio and dependencies on every system out there instantly! We all would!

Why can’t Pybombs check for this sort of thing? 

It does.

It shouldn’t be difficult to develop a script to find old installations and highlight them.

Well, sadly, it is. It is nearly impossible to do so reliably :( Pybombs, aside from those packages that are explicitly marked for source building, checks for "native" packages!
You *can* usually install GNU Radio from source into a prefix using Pybombs next to a "native" packet. But looking at your PYTHONPATH, your system has gone through multiple iterations of that scheme, and now is seriously messed up. Sorry to say that. It's not pybombs. It's that your system, through all of the attempts of varying success at installing things parallely to your distro's installation directories has become so atypical. It's very important to me to stress this isn't "your fault" or anything. It's just that you and we have probably spent more time than reasonable at "fixing" that system instead of drawing a line somewhere clearly stating that it now would pay to make a clean-slate installation. :(

You might say it’s just me but maybe I am the 1% that has looked at it, tried and failed but didn’t then give up. I meet many people who would like to use gnuradio but just find it gets too difficult very quickly.

I know! I hope we can sort this out quickly!

 

For those who like me who just want to get on with life and not spend day or two learning about the intricacies of cmake – the old method of installing blocks:

 

mkdir build

cd build

cmake ../

make

sudo make install

 

needs to be replaced by:

 

mkdir build

cd build

cmake ../ -DCMAKE_INSTALL_PREFIX=/wherever/you/installed/gnuradio

make

make install

Correct! If you don't want to install into the system default non-distro prefix but into your private prefix, you need to tell your build system.

 

Since it became standard to build in a non default prefix, not /usr/local/  90% of the information on the web about how to do this is out of date.



:(

Best regards,
Marcus

reply via email to

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