Re: Hello! What can I do with wxPerl+Windows right now?

--0000000000001f3fe806295ebfbf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Johan Vromans <[email protected]=
> 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 executi=
on
> > 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 t=
he
> 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://oliverbetz.de/pages/Artikel/ExifTool-for-Windows
>


--=20
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.

--0000000000001f3fe806295ebfbf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi, sorry for the late reply. Thank you for the repli=
es.</div><div><br></div><div>I guess what I am suggesting is that there is =
a real need for well documented, end-to-end workflows that are platform spe=
cific. My need happens to be for Windows. A Mac workflow would be great, to=
o.</div><div><br></div><div>What does this look like to me? It&#39;d cover:=
<br><br></div><div>1. installation steps of a development environment on th=
e OS (e.g., Windows)<br></div><div>2. some notes about dev workflow (e.g., =
I like to start with wxGlade that dumps Perl, but there might be a better w=
ay; I can get this working on Ubuntu and Windos under Mobaxterm&#39;s insta=
lled Perl packages - which are cygwin based)<br></div><div>3. finally, the =
actual steps of packaging this up for distribution - be it .exe, .msi, etc =
(for Windows is my main interest)</div><div><br></div><div>My Problem is co=
nceptually, I understand all the bits and pieces but always fall flat when =
it&#39;s time to roll a distro. I want to generate a Windows distribution t=
hat is just a .exe and that I can distribute as a single file. A .msi or in=
stallation bundle that handles everything would also be good, I just have n=
o idea how to generate it.</div><div><br></div><div>I guess I just need som=
e major hand holding initially; but once I figure it out I am happy to docu=
ment it and maybe even share any tools I create to help myself with the loc=
al process.<br></div><div><br></div><div>Thanks!<br></div><div>Brett<br></d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Sat, Nov 23, 2024 at 3:34=E2=80=AFPM Johan Vromans &lt;<a href=3D"mai=
lto:[email protected]" target=3D"_blank">[email protected]</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 22 =
Nov 2024 10:46:39 -0500, Don Peddicord wrote:<br>
<br>
&gt; The project I am<br>
&gt; on created a wrapper for the Perl interpreter which limited its execut=
ion<br>
&gt; to only the code we provide as part of our application.<br>
<br>
I have a similar approach for my ChordPro tool based on Oliver<br>
Betz&#39; portable perl loader as used in the standalone exiftool program.<=
br>
<br>
Basically I let the PAR packager collect everything needed, then unpack the=
<br>
package to create a file hierarchy, add special libraries and create an<br>
installer (InnoSetup for Windows, DMG for macOS).<br>
<br>
There are several tricks involved to patch/relocate dynamic libraries to<br=
>
make sure the program will only use the packaged libraries.<br>
<br>
From the perspective of the end user it is a single thing that gets<br>
installed, and a single desktop icon to click to start the program.<br>
<br>
<a href=3D"https://www.chordpro.org" rel=3D"noreferrer" target=3D"_blank">h=
ttps://www.chordpro.org</a><br>
<a href=3D"https://oliverbetz.de/pages/Artikel/ExifTool-for-Windows" rel=3D=
"noreferrer" target=3D"_blank">https://oliverbetz.de/pages/Artikel/ExifTool=
-for-Windows</a><br>
</blockquote></div><div><br clear=3D"all"></div><br><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr">This email message is for the sole use of the intended recip=
ient(s) and may contain confidential and privileged information. Any unauth=
orized use or disclosure is prohibited. If you are not the intended recipie=
nt, please contact the sender by reply email and destroy all copies of the =
original message. Thank you.<br></div></div>

--0000000000001f3fe806295ebfbf--