-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/31/2015 12:40 PM, Thomas Kluyver wrote: > At a guess: pygame probably loads those libraries dynamically when > they're required to play a file. That means that cx_Freeze can't > detect that they're required. cx_Freeze doesn't know about pygame > specifically, it just looks at what libraries are linked.
It's worth noting that a previous, successful build I have includes the relevant DLLs: http://download.savannah.gnu.org/releases/pacewar/1.5/pacewar-1.5.2-win32.zip No manual action on my part was needed at the time. I don't remember for sure what versions of cx_Freeze and Pygame I was using, so it could be that I was using version 1.9.1 instead of one of the 1.9.2 alphas. But assuming this is indeed a problem caused by a change in Pygame since version 1.9.1, is there a better solution to this than doing this sort of manual clean-up? Especially considering that these DLLs are located in Pygame's directory, it seems there must be something that can be done. Maybe something to tell cx_Freeze to assume that all DLLs found in a package's directory are required? Or maybe just assume that to be the case by default? - -- Julian Marchant https://onpon4.github.io Protect your privacy with GnuPG: https://emailselfdefense.fsf.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJV5IlpAAoJELP1a+89AVMCi28H/3v9y1H7zoUKd2kstUvnLJ9e n5zoy3gS+ur1tj+xCrW4M1pW9ZfilsmhwL8HtiRflXp+zSQiwK/qsEgAYv2QFLDq FpCA5JOE0fE+JQDpCLgt6A9TTl8TfvXigo+TMKhc8tCplqCZgHPxlekWftim7ceh aKvy0Ds9hg4fj5b2UT8iMrM9I1efseM3puzkGnvTlRKvNr4LT6XL05N87g5d71e+ 9K9KePlG8edb2FwDnQoWHwxCBMFVaipMoc45adFLRANEjZxEZy3vj2UfdFA7OCLX u3HTN46mZCtQmfVvD03pfLmgXpKbR/XXHWKOJVdSPKYo5VQVz/O1tazPiPMbrNk= =61qa -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ _______________________________________________ cx-freeze-users mailing list cx-freeze-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
