Will do. I'll take a crack at it this weekend. I suppose the tricky bit not be implementing this for source-based build and install, but for a package-based install where source is not left behind. Maybe in that case, the doc example/reference links can point to the public repo.
Very Respectfully, Dan CaJacob -- This email contains sensitive proprietary and confidential information. The technical data contained herein is/may be controlled under the U.S. International Traffic in Arms Regulations (ITAR) and may not be exported to a Foreign Person, either in the U.S. or abroad, without the proper authorization by the U.S. Department of State. -- On Wed, Feb 27, 2013 at 1:56 PM, Johnathan Corgan <johnat...@corganlabs.com>wrote: > On Wed, Feb 27, 2013 at 10:49 AM, Dan CaJacob <dan.caja...@gmail.com>wrote: > > >> I have always wanted an auto-magically generated list of references to >> other blocks/examples that use the block being documented. I think this >> would be easy to do in python. When building the docs, a script could >> search for instances of each block in other blocks and examples, then >> insert them as references in the block's documentation. >> > > Great idea. Let us know if you do any work towards this--I'd be happy to > review and see how to integrate it into the main GNU Radio software base. > > Johnathan >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio