> Well, there is one more thing you need to understand about how > cx_Freeze handles the collection of binary dependencies. :-) It uses > ldd to determine the list of shared objects that the extension module > requires, then filters them out by their location. Shared objects > found in /usr/lib and /lib are normally excluded. You can turn this > off but doing so would require that everything and the kitchen sink be > included -- likely not what you want. If there are things that are > found in /usr/lib or /lib that you want included, you will have to use > setup.py to tell cx_Freeze you want them included. I cannot tell which > shared objects you want and which ones you don't want, after all! :-)
Anthony, thanks again for clarifying how cx_freeze handles binary dependencies. I was able to package my application as needed. I would like to propose an approach on that may be able to automatically tell which shared objects an application wants. The idea is to have cx_freeze automatically generate a simple "Hello World" application that imports no libraries, to build it, and then to examine the application's binary with ldd. The library dependencies reported by ldd would be the minimum dependencies any application needs. Then, it would be possible to compare this list of dependencies with the dependencies needed by the actual application binaries packaged with cx_freeze, and identify and package the libraries that are added in such a more "complex" application. ------------------------------------------------------------------------------ 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
