low speed testing.
However, I have been able to get gnuradio-core, as well as several other gr-* packages to compile.
The most problem seemed to be centered on having 1) a somewhat large set of additional packages
that don't seem to have much to do with signal processing, such as various cpp pre-preprocessing
tools, or the like. If the intent was to have a package that was 'portable', then having a large number
of ancillary packages, which have not only interdependencies, but also mutual exlucusions for an
existing system configuration, seems to go counter to that goal.
Since I don't have much (like absolutely none) of anything based on an existing installed python
environment, the fact that a number of libraries and packages where 'installed' to get things for
gnuradio to compile correctly, it is of no real great difficulty, other than just which ones, and what
upstream package requirements are needed.
Moving on... Since I don't have hardware at the moment, are there some examples of using simulated
signal generators or the like in the existing cvs packages, or out on the net. Also, the gnuradio web site
has some pictures of oscope, or fft output, are those buried some where in the gr-* set of code.
Perhaps next week I'll have the time to see if I can set this up on a NetBSD machine, but in the mean
time I'd like test things on the linux box I have at the moment.
Thanks
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
