On 03/15/2012 02:14 PM, Porges, Donald wrote: > I've read that, and it only applies to telling grc where the xml is > for a non-hierarchical block; that is, it solves a build-time > problem, not a runtime problem. > > > On Mar 15, 2012, at 5:07 PM, Tom Rondeau wrote: > > On Thu, Mar 15, 2012 at 3:28 PM, Porges, Donald > <donald.por...@analog.com<mailto:donald.por...@analog.com>> wrote: > Hi, > > I'm trying to figure out a good way to distribute some custom heir > blocks that go with my low-level custom blocks I've written. The > issue is that the xml and py files are both generated into my > ~/.grc_gnuradio directory, and the xml files contain lines like > > execfile("/Users/myname/.grc_gnuradio/file.py") >
Well, this is my doing, and I can't say I love it. The idea was that user didnt need to set their PYTHONPATH. This would be a code change, but it could be better replaced by "from file import class". Here is the relevant line: http://gnuradio.org/cgit/gnuradio.git/tree/grc/python/convert_hier.py#n39 I guess the additional thing is that the generated client code also append os.path.join(os.expanduser('~'), '.grc_gnuradio') to the sys.path, so the imports would still work when the PYTHONPATH env var isnt set. -josh _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
