hi all, when i used to do this......i'm thinking 2018, my process was this:
1. windows OS and installed citrusperl. why citrusperl? because i could never get the wx widgets and alien bits to build on my dev box - and yes, i wasted days trying. 2. normal processes to develop the perl script, wxFormBuilder tool to help create the gui xrc, coz that's how i liked to load the gui components - but anything (glade, handcrafting, etc) will do. make sure the script runs as expected. i had some fairly cool multi-threaded apps running and they are (surprisingly) still in daily use at a big customer! 3. to build the EXE, you need to launch a citrus terminal as administrator (important but afraid I don't recall why), like this: C:\citrusPerl\perl\bin\citrusterm.bat then, to build with an annoying popup command prompt, do this: wxpar --gui -o Migration.exe Migration_tool.pl or, to build without an annoying popup command prompt, do this: wxpar -o Migration.exe Migration_tool.pl hope that's useful - or at least a pointer to the things we need to bring up to date - or a list of what not to do? :) cheers, Darren On 16 Dec 2024, at 08:12, Brett Estrade <brett.estr...@gmail.com> wrote: Hi, sorry for the late reply. Thank you for the replies. I guess what I am suggesting is that there is a real need for well documented, end-to-end workflows that are platform specific. My need happens to be for Windows. A Mac workflow would be great, too. What does this look like to me? It'd cover: 1. installation steps of a development environment on the OS (e.g., Windows) 2. some notes about dev workflow (e.g., I like to start with wxGlade that dumps Perl, but there might be a better way; I can get this working on Ubuntu and Windos under Mobaxterm's installed Perl packages - which are cygwin based) 3. finally, the actual steps of packaging this up for distribution - be it .exe, .msi, etc (for Windows is my main interest) My Problem is conceptually, I understand all the bits and pieces but always fall flat when it's time to roll a distro. I want to generate a Windows distribution that is just a .exe and that I can distribute as a single file. A .msi or installation bundle that handles everything would also be good, I just have no idea how to generate it. I guess I just need some major hand holding initially; but once I figure it out I am happy to document it and maybe even share any tools I create to help myself with the local process. Thanks! Brett On Sat, Nov 23, 2024 at 3:34 PM Johan Vromans <jvrom...@squirrel.nl <mailto:jvrom...@squirrel.nl>> wrote: > On Fri, 22 Nov 2024 10:46:39 -0500, Don Peddicord wrote: > > > The project I am > > on created a wrapper for the Perl interpreter which limited its execution > > to only the code we provide as part of our application. > > I have a similar approach for my ChordPro tool based on Oliver > Betz' portable perl loader as used in the standalone exiftool program. > > Basically I let the PAR packager collect everything needed, then unpack the > package to create a file hierarchy, add special libraries and create an > installer (InnoSetup for Windows, DMG for macOS). > > There are several tricks involved to patch/relocate dynamic libraries to > make sure the program will only use the packaged libraries. > > From the perspective of the end user it is a single thing that gets > installed, and a single desktop icon to click to start the program. > > https://www.chordpro.org <https://www.chordpro.org/> > https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows -- 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.
