From: John H. <jo...@co...> - 2004-08-17 09:07:46
|
On Mon, 16 Aug 2004, Patrick Hartling wrote: > On Mon, 2004-08-16 at 17:34 +0100, John Hodrien wrote: >> On Mon, 16 Aug 2004, Patrick Hartling wrote: >> >>> John Hodrien wrote: >>>> How do you build the python bindings? I'm currently running: >>>> >>>> scons EnablePython=True BoostPythonDir=/blah/ >>>> >>>> But I'm not getting anything sensible built. What should I be running to >>>> get >>>> the python bindings out? >>> >>> That is the correct way to build the bindings. What results are you >>> getting? >> >> Right, I'm clearly not understanding what I'm doing enough, so I'll be more >> verbose. I'm not a python coder, that's something I'm needing to learn, so >> bear with any idiocy I put across. Sadly things are being done a little >> backwards. >> >> I've downloaded gmtl, untarred, and run >> scons EnablePython=True BoostPythonDir=/blah/ >> >> What should I expect to be created? I get a gmtl.so which is mammoth (161Mb) >> and nothing else I can see of merit. > > That's exactly what you should expect. That .so file can be loaded by > Python as an extension. You just need to put it somewhere (/usr/lib/ > pythonX.Y/site-packages is a likely place) that Python can find it at > run time. You can also set the $PYTHONPATH environment variable to > extend Python's module search path. Hmm, it was failing to pick it up, and was complaining about no module name gmtl. I'll have another attack at it. Cheers, jh -- "I mean, if 10 years from now, when you are doing something quick and dirty, you suddenly visualize that I am looking over your shoulders and say to yourself, "Dijkstra would not have liked this", well that would be enough immortality for me." -- Edsgar Wybe Dijkstra |