shared components in "compiled" executables.

--===============1020989705==
Content-Type: multipart/alternative;
boundary="----=_Part_1902_24914745.1213810840978"

------=_Part_1902_24914745.1213810840978
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was
wondering whether the following was possible:

I would like to be able to share components between executables of the same
overarching 'application'. As it stands right now, I have several apps that
are all related together, and hence could reuse each others' components. But
since they are all compiled separately, they all bundle (repeatedly) the
same perl executable, shared libraries, etc.

How do you make it so that each library in one app is viewable/usable by the
others, and hence does not need to be archived separately?

Thanks much,

Ed

------=_Part_1902_24914745.1213810840978
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was wondering whether the following was possible:

I would like to be able to share components between executables of the same overarching 'application'. As it stands right now, I have several apps that are all related together, and hence could reuse each others' components. But since they are all compiled separately, they all bundle (repeatedly) the same perl executable, shared libraries, etc.


How do you make it so that each library in one app is viewable/usable by the others, and hence does not need to be archived separately?

Thanks much,

Ed


------=_Part_1902_24914745.1213810840978--

--===============1020989705==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1020989705==--

RE: shared components in "compiled" executables.

This is a multipart message in MIME format.

--===============1843639371==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0AD2_01C8D131.092A7800"
Content-Language: en-ca

This is a multipart message in MIME format.

------=_NextPart_000_0AD2_01C8D131.092A7800
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Check out the--scan, --shared, --use and -runlib options.



I thought I posted a sample for this to the PDK list, but the best I can find right now is this:



http://aspn.activestate.com/ASPN/Mail/Message/pdk-beta/33552 75



Note that you don't need to have a separate shared lib; you could try to bundle as much as you can into one of your applications and
just use that one. Conceptually I prefer a separate lib though.



Cheers,

-Jan



From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounces@listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: June 18, 2008 10:41 AM
To: activeperl@listserv.activestate.com
Subject: shared components in 'compiled' executables.



hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was wondering whether the following was possible:

I would like to be able to share components between executables of the same overarching 'application'. As it stands right now, I
have several apps that are all related together, and hence could reuse each others' components. But since they are all compiled
separately, they all bundle (repeatedly) the same perl executable, shared libraries, etc.

How do you make it so that each library in one app is viewable/usable by the others, and hence does not need to be archived
separately?

Thanks much,

Ed


------=_NextPart_000_0AD2_01C8D131.092A7800
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">


charset=3Dus-ascii">

RE: shared components in "compiled" executables.

--===============1495919968==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Dexc hewr04data_"

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Dexchewr04da ta_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ed,

That option is directly supported by perlapp / pertray (see the User Guide)=
..

What I do is compile all my common modules and the perl10.dll inside of a s=
ingle (or many) dll file(s) in one project . On the 'Options 2' tab ensure=
that you select 'Only share with my own executables (those generated with =
this PDK license)' or 'Share with anybody'.

Then in another project I add that dll to the 'Module Search Path' and ensu=
re to 'Exclude perl510.dll from executable' on the 'Size' tab. Finally on =
the 'Options 1' tab ensure to select 'Use run library' and give a relative =
path to where your application can find the required dll(s). I simply use =
"." to look in the local directory.

--Joel

From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounce=
s@listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl@listserv.activestate.com
Subject: shared components in 'compiled' executables.

hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was won=
dering whether the following was possible:

I would like to be able to share components between executables of the same=
overarching 'application'. As it stands right now, I have several apps tha=
t are all related together, and hence could reuse each others' components. =
But since they are all compiled separately, they all bundle (repeatedly) th=
e same perl executable, shared libraries, etc.

How do you make it so that each library in one app is viewable/usable by th=
e others, and hence does not need to be archived separately?

Thanks much,

Ed

________________________________
This message may contain confidential or privileged information. If you are=
not the intended recipient, please advise us immediately and delete this m=
essage. See http://www.datapipe.com/emaildisclaimer.aspx for further inform=
ation on confidentiality and the risks of non-secure electronic communicati=
on. If you cannot access these links, please notify us by reply message and=
we will send the contents to you.

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Dexchewr04da ta_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spread sheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/oi s/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/dire ctory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas=
..microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.or=
g/2001/04/xmlenc#" xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xm=
lns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http=
://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf=3D"http://schemas.micros=
oft.com/data/udc/xmlfile" xmlns:wf=3D"http://schemas.microsoft.com/sharepoi=
nt/soap/workflow/" xmlns:mver=3D"http://schemas.openxmlformats.org/markup-c=
ompatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/o=
mml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/200 6/relation=
ships" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/service s/2006/t=
ypes" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/service s/2006/me=
ssages" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns=3D"http://www.w3.org/T=
R/REC-html40">

>

RE: shared components in "compiled" executables.

This is a multipart message in MIME format.

--===============0925685358==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0AEB_01C8D133.953E3B40"
Content-Language: en-ca

This is a multipart message in MIME format.

------=_NextPart_000_0AEB_01C8D133.953E3B40
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Joel,



Excluding perl510.dll is no longer necessary in PDK 7. It may provide a performance benefit if you don't use --dyndll, but with
dynamic DLL loading using a bundled shared perl510.dll should not have any noticeable disadvantage.



However, if you include perl510.dll separately, then using '.' as the runlib is bad practice: if you add your application directory
to the PATH, and you also have a local Perl installation on the PATH, then you may break either your application, or the Perl
installation if they are not of the same version, depending on which directory is listed first in the PATH. You avoid this issue by
using a separate runlib directory.



Cheers,

-Jan



PS: This discussion should really be moved to the PDK mailing list.



From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounces@listserv.ActiveState.com] On Behalf Of Joel Friedman
Sent: June 18, 2008 10:54 AM
To: 'Edward Peschko'; activeperl@listserv.activestate.com
Subject: RE: shared components in 'compiled' executables.



Ed,



That option is directly supported by perlapp / pertray (see the User Guide).



What I do is compile all my common modules and the perl10.dll inside of a single (or many) dll file(s) in one project . On the
'Options 2' tab ensure that you select 'Only share with my own executables (those generated with this PDK license)' or 'Share with
anybody'.



Then in another project I add that dll to the 'Module Search Path' and ensure to 'Exclude perl510.dll from executable' on the 'Size'
tab. Finally on the 'Options 1' tab ensure to select 'Use run library' and give a relative path to where your application can find
the required dll(s). I simply use "." to look in the local directory.



--Joel



From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounces@listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl@listserv.activestate.com
Subject: shared components in 'compiled' executables.



hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was wondering whether the following was possible:

I would like to be able to share components between executables of the same overarching 'application'. As it stands right now, I
have several apps that are all related together, and hence could reuse each others' components. But since they are all compiled
separately, they all bundle (repeatedly) the same perl executable, shared libraries, etc.

How do you make it so that each library in one app is viewable/usable by the others, and hence does not need to be archived
separately?

Thanks much,

Ed



_____

This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately
and delete this message. See http://www.datapipe.com/emaildisclaimer.aspx for further information on confidentiality and the risks
of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the
contents to you.


------=_NextPart_000_0AEB_01C8D133.953E3B40
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spread sheet" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/x ml" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/oi s/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/di rectory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/20 02/1/alerts/"=
xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile " =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/wor kflow/" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compa tibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/200 6/relationshi=
ps" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/service s/2006/types"=
=
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/service s/2006/messag=
es" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns=3D"http://www.w3.org/TR/REC-html40">


charset=3Dus-ascii">

RE: shared components in "compiled" executables.

--===============0265125371==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Eexc hewr04data_"

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Eexchewr04da ta_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jan,

I am using a bundled shared perl10.dll in one of my library files (a dll wi=
th other modules in it as well). I am specifically excluding perl510.dll f=
rom my executable so I don't waste the 873k of space in my binary and in ot=
her dll's.

Good point on the runlib path. In this particular instance, my application=
is not in the PATH, nor is perl locally installed on the machine - hence t=
he reason it's complied in the first place J But I can see your point on b=
ad practice.

Thanks for your insight,

--Joel

PS - nice work on the MS scripting games. I managed to get them all (and w=
in a copy of Vista Ultimate in the process), but they weren't as clean as y=
ours.

From: Jan Dubois [mailto:jand@activestate.com]
Sent: Wednesday, June 18, 2008 2:08 PM
To: Joel Friedman; 'Edward Peschko'; activeperl@listserv.activestate.com
Subject: RE: shared components in 'compiled' executables.

Hi Joel,

Excluding perl510.dll is no longer necessary in PDK 7. It may provide a pe=
rformance benefit if you don't use --dyndll, but with dynamic DLL loading u=
sing a bundled shared perl510.dll should not have any noticeable disadvanta=
ge.

However, if you include perl510.dll separately, then using '.' as the runli=
b is bad practice: if you add your application directory to the PATH, and y=
ou also have a local Perl installation on the PATH, then you may break eith=
er your application, or the Perl installation if they are not of the same v=
ersion, depending on which directory is listed first in the PATH. You avoid=
this issue by using a separate runlib directory.

Cheers,
-Jan

PS: This discussion should really be moved to the PDK mailing list.

From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounce=
s@listserv.ActiveState.com] On Behalf Of Joel Friedman
Sent: June 18, 2008 10:54 AM
To: 'Edward Peschko'; activeperl@listserv.activestate.com
Subject: RE: shared components in 'compiled' executables.

Ed,

That option is directly supported by perlapp / pertray (see the User Guide)=
..

What I do is compile all my common modules and the perl10.dll inside of a s=
ingle (or many) dll file(s) in one project . On the 'Options 2' tab ensure=
that you select 'Only share with my own executables (those generated with =
this PDK license)' or 'Share with anybody'.

Then in another project I add that dll to the 'Module Search Path' and ensu=
re to 'Exclude perl510.dll from executable' on the 'Size' tab. Finally on =
the 'Options 1' tab ensure to select 'Use run library' and give a relative =
path to where your application can find the required dll(s). I simply use =
"." to look in the local directory.

--Joel

From: activeperl-bounces@listserv.ActiveState.com [mailto:activeperl-bounce=
s@listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl@listserv.activestate.com
Subject: shared components in 'compiled' executables.

hey all,

I've been using perlapp/perltray/etc. to 'compile' executables, and was won=
dering whether the following was possible:

I would like to be able to share components between executables of the same=
overarching 'application'. As it stands right now, I have several apps tha=
t are all related together, and hence could reuse each others' components. =
But since they are all compiled separately, they all bundle (repeatedly) th=
e same perl executable, shared libraries, etc.

How do you make it so that each library in one app is viewable/usable by th=
e others, and hence does not need to be archived separately?

Thanks much,

Ed

________________________________
This message may contain confidential or privileged information. If you are=
not the intended recipient, please advise us immediately and delete this m=
essage. See http://www.datapipe.com/emaildisclaimer.aspx for further inform=
ation on confidentiality and the risks of non-secure electronic communicati=
on. If you cannot access these links, please notify us by reply message and=
we will send the contents to you.

________________________________
This message may contain confidential or privileged information. If you are=
not the intended recipient, please advise us immediately and delete this m=
essage. See http://www.datapipe.com/emaildisclaimer.aspx for further inform=
ation on confidentiality and the risks of non-secure electronic communicati=
on. If you cannot access these links, please notify us by reply message and=
we will send the contents to you.

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Eexchewr04da ta_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spread sheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/oi s/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/dire ctory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas=
..microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.or=
g/2001/04/xmlenc#" xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xm=
lns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http=
://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf=3D"http://schemas.micros=
oft.com/data/udc/xmlfile" xmlns:wf=3D"http://schemas.microsoft.com/sharepoi=
nt/soap/workflow/" xmlns:mver=3D"http://schemas.openxmlformats.org/markup-c=
ompatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/o=
mml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/200 6/relation=
ships" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/service s/2006/t=
ypes" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/service s/2006/me=
ssages" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns=3D"http://www.w3.org/T=
R/REC-html40">

>