Mark Erbaugh wrote:
You can use a shell script to launch your app, and set
LD_LIBRARY_PATH in the script before launching the real app. There is also a way to change the library path names in the extension modules so they look
for them in a different place, although IIRC it is a non-standard tool so you may have to hunt for it a bit. Search the archives of this list
for more details. I think it is called chrpath.Robin,
Thanks for the reply. I've seen some information the LD_LIBRARY_PATH
should not be used for 'production' installation, that it is really
designed for development, so I wonder if that is really the way to go.
It's done more often than you might think. For example, unless they've changed it recently the Mozilla apps are usually launched this way.
The libraries that are giving me problems are:
libpython2.4.so.1.0
libsybdb.so.5
libpq.so.4Obviously, the problem with libpython2.4 is that I've developed the
application with Python 2.4, but newer installations of Linux have
Python 2.5 as standard.
If you build your own Python without the shared library configure option, and then use that to do your freezing, then the full Python executable will be part of your frozen app.
The others I don't know enough about to give suggestions.
ยทยทยท
On Tue, 2008-06-10 at 12:20 -0700, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!