Re: [PyGiNaC-users] Static library possible?
Status: Alpha
Brought to you by:
jbrandmeyer
From: Jonathan B. <jbr...@ea...> - 2005-09-19 03:19:02
|
On Mon, 2005-09-19 at 00:27 +0200, Richard B. Kreckel wrote: > Hi! > > Is there a place where I can read more about how the lookup of the > library works, when one invokes a Python 'from ginac import...' command? Libraries in Python are called "modules", initially covered in Section 6 of the Python Tutorial. See also "Creating Packages" in the Boost.Python tutorial, sys.path in the Python Library Reference, and "Modifying Python's Search Path" in the Installing Python Modules manual. If it isn't clear from the Boost.Python docs, the entry point function in a Boost.Python extension is identified with the BOOST_PYTHON_MODULE macro. > I guess it is not possible to use any of this stuff with static library. Compiled Python modules are typically dynamically loaded shared libraries. There is a mechanism for preloading a static lib into the Python interpreter if you _really_ need to do so, but it requires relinking the interpreter every time you rebuild the extension module and is generally a royal PITA to use. > PS: The top-level run script has PYTHONPATH misspelled as PYHTONPATH. Fixed, thanks. HTH, -Jonathan |