Hi

The post you pointed at has to to with packaging your own Perl script into an executable and hide the console. This is not my problem as it is already working fine. From my no-GUI executable (packed with pp) I start other third-party executables (that I can not manipolate/compile/modify them). When they run, however, they open the console to perform their task. BUT: if I pack my own executable with PerlApp, if this executable starts the same third parties executable, NO console is shown. This is what I am trying to achieve with the same application packed with pp.

I hope it is more clear now.

Interesting, can you show how you package a bare minimum test case which replicates what you are seeing with the perlapp build? I'd be interested in seeing a packaged (via perlapp) version of the minimal example, perhaps it's something that can be replicated in another tool.

Hi Marto

I do not have PerlApp anymore to create an executable. When I used to, this feature (which was not to be set explicitly anywhere) just worked. Actually we never thought about it and gave it for granted. Now that I work on my own and faced the same situation, I noticed that pp does not work the same.

The post you pointed at has to to with packaging your own Perl script into an executable and hide the console.

Hi

Thats the top of the post, the replies section on the other hand ;)

Yes, you were right! As a temporary solution I reverted to use one of the suggestions in the replies (using Win32::Exe to modify the third party executables. It works fine, however I would be more at easy if I could replicate what PerlApp did: suppress all consoles even for third party exe launched by the application created by PerlApp.

Why not try a more Windows-eske vbs solution?