I too have found that PAR can miss some modules. I ended up creating a list of required XS modules and all of my application modules explicitly.
Though I was trying to implement an improved PAR::Packer ( Active State product)

Don Peddicord 

On Jan 8, 2025, at 4:36 PM, Ralph Walden via wxperl-users <wxperl-users@perl.org> wrote:


Some additional notes on installing:

- Ensure that there is no wxwin environment variable set pointing to an older or 32-bit version of wxWidgets (e.g., leftover from citrus_perl)
- If you have gcc installed somewhere else, change the path to Strawberry\c\bin before installing
- If LWP::Protocol::https fails download the two tar files and install them from a local directory
- Building and testing doesn't show progress, and appears to only use a single CPU, so it takes a *long* time with no indication that progress is being made.

On Saturday, January 4th, 2025 at 12:21 PM, Brett Estrade <brett.estr...@gmail.com> wrote:
Thank you so much to Johan, I got going with the "quick start" cpanm commands.

Yes, they took a while to run, but necessarily so.

Feedback:
  1. I installed Wx::Demo, and it worked - wxperl_demo.pl ran as soon as I tried it, I didn't need to mess with any paths or deal with icon errors
  2. I got wxGlade 1.1.0 running, but not with Python 3.13 (some kind of WindowIterator error, idk); I had to use the latest Python 3.12
  3. a simple test "wxglade_out.pl" ran just fine also
  4. wxpar will generate an EXE, but see below for the problem description
Questions:
I figured out wxpar is available via 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 have to include Wx:: modules explicitly, e.g., wxGlade wants to use EXPORTER tags; but when I run the .exe created by wxpar, it complains about missing things like Wx::DND, Wx::FS, etc. Is it just a known thing to have to explicitly declare modules when packaging up to an EXE?
  • 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.
Thanks again, looking forward to getting these issues resolved. In the meantime, I will be working on some test applications on the Windows set up so I build up to creating what I actually have in mind.

Cheers,
Brett
--
This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.

Reply via email to