[Top][All Lists]

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

Re: [Discuss-gnuradio] "How to Write a Signal Processing Block" vaguenes

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] "How to Write a Signal Processing Block" vagueness
Date: Tue, 19 Aug 2008 10:49:39 -0700
User-agent: Mutt/1.5.17 (2007-11-01)

On Tue, Aug 19, 2008 at 11:03:42AM -0500, Jason Uher wrote:
> On Mon, Aug 18, 2008 at 9:41 PM, Randy Heiland <address@hidden> wrote:
> > Python is looking for a module literally named "my_new_package".  You should
> > simply substitute "my_new_package" with whatever Python module/file (e.g.
> > cool_block.py) that you write.  And you might want to create/keep your
> > module in a local directory and simply append that directory path to your
> > PYTHONPATH environment variable.
> >
> Right, but I think the package is literally named "my_new_package"
> "/usr/local/lib/python2.4/site-packages/gnuradio/" is in my PYTHONPATH;
> In that directory I have the following (from make install)
> _my_new_package.la
> _my_new_package.so
> my_new_package.py
> my_new_package.pyc
> my_new_package.pyo

Is the rest of the gnuradio stuff there?


  from gnuradio import gr


Are you on a 64-bit machine?

Can you send the complete backtrace that you get when you try the import?

> My .i file specified the module as
> "GR_SWIG_BLOCK_MAGIC(my_new_package,tx_encoder)"
> As for appending to PYTHONPATH, I tried that first and got the same
> error, so I figured a make install would fix it.
> Is there something that I need to update a file somewhere so python
> can find these?
> Lastly, if I do change the new module later, is it sufficient to
> simply 'make install' again (overwrite), or do I have to make
> uninstall the old module before I edit it?

Generally make install is suffcient.


reply via email to

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