wasm-demo/demo/ermis-f/python_m/cur/0172

40 lines
1.5 KiB
Plaintext
Raw Permalink Normal View History

From: pboddie at my-dejanews.com (Paul Boddie)
Date: Mon, 19 Apr 1999 15:13:01 GMT
Subject: Problem with FNORB
References: <19990419073413.22923.00002720@ng-fz1.aol.com>
Message-ID: <7ffh5k$d7k$1@nnrp1.dejanews.com>
Content-Length: 1281
X-UID: 172
In article <19990419073413.22923.00002720 at ng-fz1.aol.com>,
alhopiteau at aol.com (Alhopiteau) wrote:
> i have a problem with fnorb, running the example i get a error while the
script
> try to import the Fnorb.cdr module, this module is developped using C, how to
> manage this?
If you mean that when you try to execute a program which imports various
Fnorb modules, you get errors complaining about the whereabouts of the cdr
module, then you should ensure that your PYTHONPATH points to the directory
where cdrmodule.so is located. So, if you have cdrmodule.so in
/home/badger/Fnorb then you must make sure that /home/badger/Fnorb is in your
PYTHONPATH. Note that in the Fnorb source, cdr is not used as if it belongs
to the Fnorb package. (import cdr is used.)
I believe that the instructions with Fnorb advise you to place the .so files
(made in Fnorb/src) either somewhere in your existing PYTHONPATH, or in the
Fnorb directory. If you choose the second of these two options then you must
modify your PYTHONPATH accordingly. I was caught out by this, but the above
solution worked for me.
--
Paul Boddie
Oslo, Norway
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own