[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Ron Economos
Subject: Re: [Discuss-gnuradio] Compiling Documentation with an OOT
Date: Mon, 28 Mar 2016 18:25:07 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

No compiler switch required. On my system, even an unmodified .h file shows up in the documentation tab.

paint block documentation


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 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?


On Mon, Mar 28, 2016 at 5:52 PM, Ron Economos <address@hidden> wrote:
You put the documentation into the .h file(s) in the gr-<name>/include/<name> directory. Here's an example.



On 03/28/2016 05:30 PM, Richard Bell wrote:
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?


Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]