Giovanni Bajo wrote: > This is not strictly a PyInstaller problem, but rather a Windows problem: > http://www.microsoft.com/msj/0698/win320698.aspx > caused by the fact that in Windows the processes are not really in a > parent/child relationship. > > Alas, there does not seem to exist a solution that can be totally > encapsulated > within PyInstaller.
Actually, the end of the article makes it sound as if there might be. Could the 5-step "solution" described there be used in winmain.c? -- Don Dwiggins Advanced Publishing Technology --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
