On Fri, 2009-05-08 at 17:47 +0200, Patrick S. wrote:
dpkg -L gnuradio
Not to complicate things, but this won’t work as expected. There are
many binary packages for Ubuntu, and the ‘gnuradio’ package is simply a
meta-package that depends on the others, for ease of installation. So
the above won’t show any real files.
The primary difference in installation location between a source install
and a binary install is in the ‘prefix’.
Source installations, unless told differently, are all rooted
at /usr/local, and the various files go into subdirectories there:
/usr/local/bin/*
/usr/local/lib/*
/usr/local/lib/python2.x/site-packages/gnuradio/*
/usr/local/include/*
/usr/local/share/gnuradio/examples/*
/usr/local/doc/gnuradio/*
/usr/local/share/usrp/*
The /usr/local hierarchy is for files that are not maintained by the
system packaging library.
When installing GNU Radio in Ubuntu from binary packages, the standard
system installation locations are used, which are all rooted at /usr,
as:
/usr/bin/*
/usr/lib/*
/usr/lib/python2.x/site-packages/gnuradio/*
/usr/include/*
/usr/share/gnuradio/examples/*
/usr/doc/gnuradio/*
/usr/share/usrp/*
This is all per the Filesystem Hierarchy Standard (FHS) and the
Debian/Ubuntu packaging policy.
The most common things a user might look for after an install of either
type are the example scripts and the utilities like usrp_fft.py.
The example scripts are installed into the locations noted above, while
the utility scripts are installed into the bin directory. Since the bin
directory is on the user’s PATH, he or she doesn’t have to actually go
to those directories to run them; instead, they can just invoke them
from whatever directory they happen to be in.
Hope this clears things up.
Johnathan