On 22 February 2010 17:41, Kris <[email protected]> wrote: [...] > I now understand what the executables need to run. But it is still not > clear to me how to distribute the executables and libraries together. > > For example, the build files contain libpython3.1.so.1.0. Clearly, this > is the python library and should be distributed. But it definitely > shouldn't be distributed in /usr/lib (e.g. as part of a .rpm), since it > would conflict with a packaged version of python. On the other hand, one > needs to guarantee that this library will be available, else the built > executables won't run: "somehow" libpython3.1.so.1.0 needs to be > distributed. > > So, where should the .so files be installed ? [...]
I think this depends on who you are targeting. If you want to target a particular Linux distribution then it's easy. Just specify dependencies on Python and the other packages you need and do not bundle them. Things become more tricky when you want to target various different distributions, perhaps with different package management systems, and maybe older distributions that don't have a Python 3.x package etc. Probably the safest way is to dump everything under /usr/lib/your-package or somewhere similar, which is basically what cx_Freeze apparently does (I have only used it under Windows so far). But this would not be the way to get your package into the official Fedora/Ubuntu/whatever repositories. -- Michael Wood <[email protected]> ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ cx-freeze-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
