[Top][All Lists]

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

Re: [Discuss-gnuradio] Problems with How to Write a Signal Processing Bl

From: Johnathan Corgan
Subject: Re: [Discuss-gnuradio] Problems with How to Write a Signal Processing Block
Date: Tue, 30 Jan 2007 16:38:32 -0800
User-agent: Thunderbird (X11/20070103)

Bahn William L Civ USAFA/DFCS wrote:

> Fine. So, per the article, "Victory! Our new block works!"
> Or does it?
> If I try to run the top level Python program, qa_howto.py, I get the
> following error message:
> ImportError: No module named howto

The operation 'make check' ultimately results in running the program
'run_tests' that lives in the src/python directory.  This is a shell
script that sets several important variables that allow the Python
interpreter to find everything in the build tree at runtime. It then
runs qa_howto.py with this modified environment.

By running qa_howto.py from the command line, you are bypassing this,
and the Python interpreter is looking for everything in the system
directory.  Since you haven't installed the newly compiled code into the
system yet, it doesn't find anything. (Even if you did, the qa_howto.py
isn't written to properly import things from there.)

So the code really is working, as evidenced by 'make check' passing.

> What do I need to do (and, more importantly, how am I supposed to know
> that I need to do it) in order to actually run the python program
> (qa_howto.py) that supposedly passed all of the make checks?

As I mentioned, 'make check' eventually *does* run qa_howto.py, in a
modified runtime environment to find things in the build tree.

Incidentally, there is a significant portion of the 2-day training
agenda/lab session that goes through all this a minute detail.


reply via email to

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