On Sat, 4 Jan 2025 14:21:47 -0600, Brett Estrade <brett.estr...@gmail.com> wrote:
> I got going with the "quick start" cpanm commands. > Yes, they took a while to run, but necessarily so. Great to hear! > I figured out wxpar is available via Wx::Perl::Packager > <https://metacpan.org/pod/Wx::Perl::Packager>, so I installed that - no > problems there. My problem comes from the executable that results from > wxpar. Do any of the following issues sounds familiar? I am not familiar with wxpar. It was stalled at the same time wxPerl and Alien::wxWidgets were abandoned and most likely do not work anymore. I use a tool to generate (part of) the PAR .pp for a wxWidgets application. It may be interesting to take a look at https://github.com/ChordPro/chordpro/tree/master/pp/windows > - After working through the above issue, the .exe I create will run but > it does nothing visible in STDOUT or in the GUI. Using the "--gui" > option will cause a process tab to appear in the bottom task bar, but > then it also goes away without showing anything. That's one of Windows annoyances. A GUI application effectively has no STDOUT and STDERR. A crash due to a missing library or module is silent.
