Alan, thanks for the input. I had been working with the full source release but I've now checked out the svn repo which has the same issue. I added <qpid-source>/python to my PYTHONPATH. I also started a qpid broker as the README.txt mentions. I do have these files being generated
ld-chhfe01:/home/spervez1/qpid-0.14 $ find . -name *engine* ./java/doc/network-driver-protocol-engine-sequence.dia ./cpp/src/qmf/engine ./cpp/src/.libs/libqmfengine.so.1.0.1 ./cpp/src/.libs/libqmfengine.so.1 ./cpp/src/.libs/libqmfengine.so ./cpp/src/.libs/libqmfengine.lai ./cpp/src/.libs/libqmfengine.la ./cpp/src/.libs/libqmfengine.so.1.0.1T ./cpp/src/libqmfengine.la ./cpp/include/qmf/engine ./cpp/bindings/qmf/python/.deps/_qmfengine_la-qmfengine.Plo ./cpp/bindings/qmf/qmfengine.i ./cpp/bindings/qmf/ruby/.deps/qmfengine_la-qmfengine.Plo ld-chhfe01:/home/spervez1/qpid-0.14 $ find ../qpid-tools -name *engine* ../qpid-tools/lib/libqmfengine.so.1.0.1 ../qpid-tools/lib/libqmfengine.so.1 ../qpid-tools/lib/libqmfengine.so ../qpid-tools/lib/libqmfengine.la ../qpid-tools/include/qmf/engine So atleast part of the qmf engine is being built. But I am totally stumped by why qmfegine.py is not being generated. Does python only need to know about the qpid 'source dir' or the 'install dir' as well? Salman -----Original Message----- From: Alan Conway [mailto:[email protected]] Sent: Friday, March 23, 2012 8:38 AM To: [email protected] Cc: Pervez, Salman Subject: Re: qmfengine On 03/22/2012 06:27 PM, Pervez, Salman wrote: > I am going to update this thread in the hopes that someone know the solution. > It looks like my qpid build does not have the file qmfengine.py installed > anywhere. From what I could see it is supposed to be generated when the > /trunk/qpid/cpp/bindings/qmf/python/ module is built. The makefile > specifically mentions qmfengine.py and qmfengine.cpp as files that will be > generated. Does anyone know why these files are not being built? What can I > do to debug this? Thanks. > If you downloaded just the C++ tarball then you don't have all the python bits. You need to download the "full source release" from qpid.apach.org and install them in a place where python can find them. Check the README in the python directory of the source release. If you're building in a checkout then the build should use the python bits from the checkout automatically. > Salman > > -----Original Message----- > From: Pervez, Salman [mailto:[email protected]] > Sent: Thursday, March 22, 2012 10:53 AM > To: [email protected] > Subject: qmfengine > > Hi everyone, I have yet another qpid install question. :) > > I am getting this error > > File "/home/spervez1/qpid-0.14/cpp/bindings/qmf/python/qmf.py", line 26, > in<module> > import qmfengine > ImportError: No module named qmfengine > > I did a quick google search and found that I needed to install > the<qpid-home>/extras/qmf module. So I did. > > /... qpid-0.14/extras/qmf $ python setup.py build > /...qpid-0.14/extras/qmf $ python setup.py install > --home=/home/spervez1/python-modules/qmf > > The $HOME/python-modules/qmf directory tree looks like this... > > Lib/ > Python/ > Qmf/ > > I've tried adding all these directories to my PYTHONPATH but still get the > same error. Fyi the python-modules/qmf/lib/python/qmf dir contains these > files... > > __init__.py __init__.pyc console.py console.pyc > > Does anyone know what I am doing wrong? Thanks! > > Salman > > ________________________________ > > CONFIDENTIALITY AND SECURITY NOTICE > > The contents of this message and any attachments may be confidential and > proprietary and also may be covered by the Electronic Communications Privacy > Act. This message is not intended to be used by, and should not be relied > upon in any way, by any third party. If you are not an intended recipient, > please inform the sender of the transmission error and delete this message > immediately without reading, disseminating, distributing or copying the > contents. Citadel makes no assurances that this e-mail and any attachments > are free of viruses and other harmful code. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
