Re: gr-iqbal, gr-fosphor, gr-osmosdr updated to Gnuradio 3.8

2020-01-07 Thread Barry Jackson

On 08/12/2019 20:31, Sylvain Munaut wrote:

Hi,

I have just pushed updates to various osmocom repositories, updating
them to run on gnuradio 3.8.


--snip


Cheers,

  Sylvain Munaut

PS: bcc'd package maintainer I thought of.



Hi,
Thanks for these updates, I maintain gnuradio etc. for Mageia.

However, is there any chance that you could please revert the commit 
that removed the .pc creation in gr-iqbal?


We use pkgconfig(gr-iqbal) style BuildRequires in our rpm spec files for 
installation during package builds where we can and are somewhat 
confused as to why you did this.


I have only looked at gr-iqbal so far, so if any of the others have had 
the same treatment then ... :)


Oh yes and I could not find any path to a release tarball for 
gr-iqbal-0.38.1.

If there is a spec. friendly one I would love to know where it is.
I can normally find them in github or SF but cgit is another story.

Thanks,
Barry



Re: gnuradio-3.8 build fails with error: cannot convert const string {aka const std::__cxx11::basic_string} to pmt::pmt_t {aka boost::shared_ptr}

2020-01-07 Thread Michael Dickens
The issue is how CMake decides to order "include_directories". There are
(if I recall correctly) 4 primary sources of these via properties: for the
directory, for individual sources, for to-be-built targets, and for linkage
targets. The ordering of these is critical, since our goal is to list
in-tree headers/linkage before out-of-tree headers/linkage. I'd have to go
back to my work to remember how CMake orders these, but what I do recall is
that the last one (for linkage targets) doesn't come last, which seems
wrong to me: any out-of-tree property should always come last in any
ordering! And, I could not figure out an easy or clean way to force the
ordering to work for our goal. It's an unfortunate confluence of moving to
"modern CMake" linkage targets and how CMake works internally. Once I'm
caught up with UHD, GR, and Volk backlog from being away for 2 weeks, I'll
look into this issue again since it's pretty critical for MacPorts that
this work! Hope this is useful and maybe makes some sense! - MLD