Re: [Discuss-gnuradio] Compiling Documentation with an OOT

On 03/30/2016 10:54 PM, Richard Bell wrote: > I've asked this question a few times now on the mailing list, and each > time I hope a different answer comes through. Each time though it's > the answer Ron gave, which never works for me. I can't figure it out. > So I've always resorted to the xml

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

Hello Richard, Some months ago we stumbled upon the same problem (see https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00227.html). Maybe our solution works for you, although a definite solution would be a good idea (ours was based on simple trial-and-error given our null knowledge

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

I've asked this question a few times now on the mailing list, and each time I hope a different answer comes through. Each time though it's the answer Ron gave, which never works for me. I can't figure it out. So I've always resorted to the xml tags to get documentation into GRC, but for the

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

On Mon, Mar 28, 2016 at 9:25 PM, Tom McDermott wrote: > Hi Richard - > > When you say 'propagate through to GRC' do you mean 'How to display on > the GRC documentation tab in the open block properties window'? (select > block, double-click, or rt-click-properties). > > I do

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

No compiler switch required. On my system, even an unmodified .h file shows up in the documentation tab. paint block documentation Ron On 03/28/2016 06:02 PM, Richard Bell wrote: Hey Ron, That's where I added my documentation, just like you have it there, but I can't get it to propagate

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

Hi Richard - When you say 'propagate through to GRC' do you mean 'How to display on the GRC documentation tab in the open block properties window'? (select block, double-click, or rt-click-properties). I do that by putting text between: in the module's XML file (manually pasted text, with

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

Hey Ron, That's where I added my documentation, just like you have it there, but I can't get it to propagate through. Do I need to compile it differently for that to happen? Is there a gnuradio setting that needs to be set for documentation to make its way through? Rich On Mon, Mar 28, 2016 at

Re: [Discuss-gnuradio] Compiling Documentation with an OOT

You put the documentation into the .h file(s) in the gr-/include/ directory. Here's an example. https://github.com/gnuradio/gnuradio/blob/master/gr-dtv/include/gnuradio/dtv/dvbt2_framemapper_cc.h Ron On 03/28/2016 05:30 PM, Richard Bell wrote: Hi all, I would like to know how I get the

[Discuss-gnuradio] Compiling Documentation with an OOT

Hi all, I would like to know how I get the comments I add to my public header function to propagate through to the GRC Block documentation tab. Is there a flag I have to add when I compile the OOT? Thanks, Rich ___ Discuss-gnuradio mailing list