On Thu, May 22, 2014 at 1:43 AM, Activecat active...@gmail.com wrote:
On Tue, May 20, 2014 at 4:29 PM, Martin Braun martin.br...@ettus.comwrote:
FYI, I don't like installing stuff to /usr/local. If you take PyBombs'
directory, and then use -DCMAKE_INSTALL_PREFIX on your own OOT, that'll
make
On Tue, May 20, 2014 at 4:29 PM, Martin Braun martin.br...@ettus.comwrote:
FYI, I don't like installing stuff to /usr/local. If you take PyBombs'
directory, and then use -DCMAKE_INSTALL_PREFIX on your own OOT, that'll
make both work and you don't have to screw around in your system's dirs.
M
On Tue, May 20, 2014 at 11:06 AM, Activecat active...@gmail.com wrote:
I've just reinstalled gnuradio yesterday, using PyBOMBS.
The newly installed version is gnuradio 3.7.4. The installation succeeded,
but it then failed to compile my custom module which worked flawlessly with
previous
On 20.05.2014 09:58, Activecat wrote:
Note:
During PyBOMBS install wizard, we are prompted for prefix, which
defaults to ../target
If we just press ENTER to accept the default value, then the prefix
becomes something like /home/user1/download/gnuradio/target.
But regardless of what has been
On Tue, May 20, 2014 at 4:29 PM, Martin Braun martin.br...@ettus.comwrote:
FYI, I don't like installing stuff to /usr/local. If you take PyBombs'
directory, and then use -DCMAKE_INSTALL_PREFIX on your own OOT, that'll
make both work and you don't have to screw around in your system's dirs.
M
On Tue, May 20, 2014 at 5:15 PM, Activecat active...@gmail.com wrote:
In this case we execute cmake
-DCMAKE_INSTALL_PREFIX=/home/user1/download/gnuradio/target ../ in the
OOT build directory.
Is there any way to hard code this install_prefix into the OOT setting
file, so that we just need
I've just reinstalled gnuradio yesterday, using PyBOMBS.
The newly installed version is gnuradio 3.7.4. The installation succeeded,
but it then failed to compile my custom module which worked flawlessly with
previous gnuradio installation.
The previous version was gnuradio 3.7.3 which was
