On Sat, 07 May 2011 00:25:19 +0200, Martin Zibricky <[email protected]> wrote:
> crypt - already merged? purpose? Already merged, and disabled by default on trunk. It basically provides a way for an executable to be encrypted through AES, with the idea that the encryption key could then be provided through custom code (eg: read over HTTP, or from a USB dongle, or whatever). In its current form, the AES key is stored within the executable itself, so the only achieved result is obfuscation. > dl - already merged? purpose? Merged & closed. It implemented dynamic loading of libpython.so within the bootloader under Linux. Previously, Linux required static linking with libpython.a, which is unavailable on most modern distros and caused lots of problems with conflicting symbols in the ELF space. > makespec_ng - ready for merging? No, it's basically just a prototype. > no_msvcrt - already merged or ready for merging? purpose? The idea was to make the bootloader much smaller under Windows by not linking it against msvcrt, relying only on Win32 API and/or the small WRT library (open-source). I've personally lost interest in it, but it's still a viable project. Part of the problem is that many uses of msvcrt/libc come from launch.c which is common code across different platforms, so it's not easy to eradicate them. > win32_unicode - not finished, bootloader part seems to be done > - fix for http://www.pyinstaller.org/ticket/298 I think I discussed this in mailing-list; I believe this is not the correct approach to fix the bug. -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
