Re: New Raspberry PI Complete OS release

[Glen Langston]

Hi Gavin,

Thanks again.

What I need is a simple function that is -not- a standard part of Gnuradio
but rather can be built in 3.7, 3.8 or 3.9. that includes a c++ module

I’d prefer these to not be identically named but rather be tagged with gnuradio 
versions,
so that I can compare the differences.  I’m working with vectors. 
This probably already exists, but it is not clear to me what is a good example.

ie I’d like:

git clone http://www.github.com/gnuradio/examplev38
cd examplev38
mkdir build
cd build
cmake ../
make -j 3 (for raspberry pi 4)
sudo make install
sudo ldconfig

then allow me to look at this code and compare it with vector
code in 3.7 and 3.9, so there would need to be

git clone http://www.github.com/gnuradio/examplev37

and 

git clone http://www.github.com/gnuradio/examplev39

These should do exactly the same thing in each of the gnuradio versions.
I’d be calling the same “examplev” block in a .grc file that would show that the
build was successful.   That is what our simple vmedian_impl.cc, vmedian_impl.h
and vectordemo_c2.grc code must do.  (in WVURAIL/gr-radio_astro)

It is just not easy to get from 3.7 to 3.8 or 3.9.   Our code is not tagged
by gnuradio version numbers, but this example code must be, so we can compare 
one
version to another (I hope we don’t need to go to sub-versions, ie 3.8.2 etc).

Again this must already exist somewhere.  I am completely perplexed by CMAKE and
XML/YAML and SWIG/PYBIND differences.

Thanks
Glen



> On Feb 3, 2021, at 6:17 PM, Gavin Jacobs <apriljunkbox@hotmail.com> wrote:
> 
> Glen,
> I'm going through a pain similar to yours.
> For working examples, you can look at the source for the blocks that are part 
> of GNU Radio. For example, the Multiply Constant block shows how to do a 
> callback, and the Add block shows how to do variable number of inputs. 
> Unfortunately, these blocks also have the complexity of allowing Vector 
> inputs, and different types of inputs, so you have to dig through that to get 
> at the parts you want. 
> 
> The closest thing I found for a working OOT module, is documented here:
> https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_C%2B%2B
> It only applies to 3.7 & 3.8, so you still have to sleuth out the differences 
> for 3.9.  Also, it does not show how to do variable # of inputs, nor a 
> parameter callback. I'm working on a block that needs those; so as soon as I 
> have it sorted out, I'll put the sources on Github.
> Guided Tutorial GNU Radio in C++ - GNU Radio
> Note: the get_minimum_distances function declaration also needs to be added 
> to the class header (my_qpsk_demod_cb_impl.h).The function 
> get_minimum_distances is a maximum likelihood decoder for the QPSK 
> demodulater. Theoretically, the function should compute the distance from 
> each ideal QPSK symbol to the received symbol (It is mathematically 
> equivalent to determining the Voronoi regions of the ...
> wiki.gnuradio.org
> 
> 
> 
> Date: Tue, 2 Feb 2021 21:19:32 -0500
> From: Glen Langston <glen.i.langston@gmail.com>
> To: Marcus Müller <mmueller@gnuradio.org>
> Cc: discuss-gnuradio@gnu.org
> Subject: Re: New Raspberry PI Complete OS release
> 
> I appreciate gr-modtool, but it is frustrating that modtool does not generate
> working code.   There really, really, really needs to be an ultra-simple 
> working
> example of C++ code for 3.8 and 3.9 that actually build.
> 
> The code could do anything, but just allow us to use it as the basis for
> creating YAML and SWIG/PYBIND code based on the new requirements.