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 [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1020989705==--

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 [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: June 18, 2008 10:41 AM
To: activeperl [at] 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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
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">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

Check out the--scan, --shared, --use and –runlib =
options.<o:p></o:p>

<o:p> </o:p>

I thought I posted a sample for this to the PDK list, but =
the
best I can find right now is this:<o:p></o:p>

<o:p> </o:p>

 <a
href=3D"http://aspn.activestate.com/ASPN/Mail/Message/pdk-be ta/3355275">h=
ttp://aspn.activestate.com/ASPN/Mail/Message/pdk-beta/335527 5</a><o:p></o=
:p>

<o:p> </o:p>

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.<o:p></o:p>

<o:p> </o:p>

Cheers,<o:p></o:p>

-Jan<o:p></o:p>

<a name=3D"_MailEndCompose"><o:p> </o:p></span=
></a>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

From:=

activeperl-bounces [at] listserv.ActiveState.com
[mailto:activeperl-bounces [at] listserv.ActiveState.com] On Behalf Of =
Edward
Peschko 
Sent: June 18, 2008 10:41 AM 
To: activeperl [at] listserv.activestate.com 
Subject: shared components in 'compiled' =
executables.<o:p></o:p>

</div>

</div>

<o:p> </o:p>

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<o:p></o:p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0AD2_01C8D131.092A7800--

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

_______________________________________________
ActivePerl mailing list
ActivePerl [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1843639371==--

--===============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 [at] listserv.ActiveState.com [mailto:activeperl-bounce=
s [at] listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl [at] 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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
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">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>

</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
Ed,<o:p></o:p>
<o:p> </o:p>
That option is directly supported by perlapp / pertray (see =
the User Guide).<o:p></o:p>
<o:p> </o:p>
What I do is compile all my common modules and the perl10.dl=
l inside of a single (or many) dll file(s) in one project . On the &#=
8216;Options 2’ tab ensure that
you select ‘Only share with my own executables (those generated with=
this PDK license)’ or ‘Share with anybody’.<o:p></o:p></=
span>
<o:p> </o:p>
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 d=
ll(s). I simply use “.” to look in the local directory.<o=
:p></o:p>
<o:p> </o:p>
--Joel<o:p></o:p>
<o:p> </o:p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
From: activepe=
rl-bounces [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.Act=
iveState.com]
On Behalf Of Edward Peschko 
Sent: Wednesday, June 18, 2008 1:41 PM 
To: activeperl [at] listserv.activestate.com 
Subject: shared components in 'compiled' executables.<o:p></o:p></sp=
an>
</div>
<o:p> </o:p>
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) the 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<o:p></o:p>
</div>
 
<hr>
This message may contain con=
fidential or privileged information. If you are not the intended recipient,=
please advise us immediately and delete this message. See http://www.datap=
ipe.com/emaildisclaimer.aspx for further
information on confidentiality and the risks of non-secure electronic comm=
unication. If you cannot access these links, please notify us by reply mess=
age and we will send the contents to you. 

</body>
</html>

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Dexchewr04da ta_--

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

_______________________________________________
ActivePerl mailing list
ActivePerl [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1495919968==--

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 [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.ActiveState.com] On Behalf Of Joel Friedman
Sent: June 18, 2008 10:54 AM
To: 'Edward Peschko'; activeperl [at] 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 [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl [at] 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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
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">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">

<style>

</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

Hi Joel,<o:p></o:p>

<o:p> </o:p>

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.<o:p></o:p>

<o:p> </o:p>

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.<o:p></o:p>

<o:p> </o:p>

Cheers,<o:p></o:p>

-Jan<o:p></o:p>

<o:p> </o:p>

PS: This discussion should really be moved to the PDK =
mailing
list.<o:p></o:p>

<a name=3D"_MailEndCompose"><o:p> </o:p></span=
></a>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

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

</div>

</div>

<o:p> </o:p>

Ed,<o:p></o:p>

<o:p> </o:p>

That option is directly supported by perlapp / pertray =
(see the
User Guide).<o:p></o:p>

<o:p> </o:p>

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’.<o:p></o:p>

<o:p> </o:p>

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.<o:p></o:p>

<o:p> </o:p>

--Joel<o:p></o:p>

<o:p> </o:p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

From:=

activeperl-bounces [at] listserv.ActiveState.com
[mailto:activeperl-bounces [at] listserv.ActiveState.com] On Behalf Of =
Edward
Peschko 
Sent: Wednesday, June 18, 2008 1:41 PM 
To: activeperl [at] listserv.activestate.com 
Subject: shared components in 'compiled' =
executables.<o:p></o:p>

</div>

<o:p> </o:p>

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<o:p></o:p>

<o:p> </o:p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

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.<o:p></o:p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0AEB_01C8D133.953E3B40--

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

_______________________________________________
ActivePerl mailing list
ActivePerl [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============0925685358==--

--===============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 [at] activestate.com]
Sent: Wednesday, June 18, 2008 2:08 PM
To: Joel Friedman; 'Edward Peschko'; activeperl [at] 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 [at] listserv.ActiveState.com [mailto:activeperl-bounce=
s [at] listserv.ActiveState.com] On Behalf Of Joel Friedman
Sent: June 18, 2008 10:54 AM
To: 'Edward Peschko'; activeperl [at] 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 [at] listserv.ActiveState.com [mailto:activeperl-bounce=
s [at] listserv.ActiveState.com] On Behalf Of Edward Peschko
Sent: Wednesday, June 18, 2008 1:41 PM
To: activeperl [at] 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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
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">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>

</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
Jan,<o:p></o:p>
<o:p> </o:p>
I am using a bundled shared perl10.dll in one of my library =
files (a dll with other modules in it as well). I am specifically exc=
luding perl510.dll from
my executable so I don’t waste the 873k of space in my binary and in=
other dll’s.<o:p></o:p>
<o:p> </o:p>
Good point on the runlib path. In this particular inst=
ance, my application is not in the PATH, nor is perl locally installed on t=
he machine – hence the reason
it’s complied in the first place J But I can see your point on bad practice.<o:p></o:p>
<o:p> </o:p>
Thanks for your insight,<o:p></o:p>
<o:p> </o:p>
--Joel<o:p></o:p>
<o:p> </o:p>
PS – nice work on the MS scripting games. I mana=
ged to get them all (and win a copy of Vista Ultimate in the process), but =
they weren’t as clean as yours.<o:p></o:p>
<o:p> </o:p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
From: Jan Dubo=
is [mailto:jand [at] activestate.com]
 
Sent: Wednesday, June 18, 2008 2:08 PM 
To: Joel Friedman; 'Edward Peschko'; activeperl [at] listserv.activestate=
..com 
Subject: RE: shared components in 'compiled' executables.<o:p></o:p>=

</div>
</div>
<o:p> </o:p>
Hi Joel,<o:p></o:p>
<o:p> </o:p>
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.<=
o:p></o:p>
<o:p> </o:p>
However, if you include perl510.dll separately, then using &=
#8216;.’ as the runlib is bad practice: if you add your application d=
irectory 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 i=
ssue by using a separate runlib
directory.<o:p></o:p>
<o:p> </o:p>
Cheers,<o:p></o:p>
-Jan<o:p></o:p>
<o:p> </o:p>
PS: This discussion should really be moved to the PDK mailin=
g list.<o:p></o:p>
<a name=3D"_MailEndCompose"></a><o:p>=
</o:p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
From: activepe=
rl-bounces [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.Act=
iveState.com]
On Behalf Of Joel Friedman 
Sent: June 18, 2008 10:54 AM 
To: 'Edward Peschko'; activeperl [at] listserv.activestate.com 
Subject: RE: shared components in 'compiled' executables.<o:p></o:p>=

</div>
</div>
<o:p> </o:p>
Ed,<o:p></o:p>
<o:p> </o:p>
That option is directly supported by perlapp / pertray (see =
the User Guide).<o:p></o:p>
<o:p> </o:p>
What I do is compile all my common modules and the perl10.dl=
l inside of a single (or many) dll file(s) in one project . On the &#=
8216;Options 2’ tab ensure that
you select ‘Only share with my own executables (those generated with=
this PDK license)’ or ‘Share with anybody’.<o:p></o:p></=
span>
<o:p> </o:p>
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 d=
ll(s). I simply use “.” to look in the local directory.<o=
:p></o:p>
<o:p> </o:p>
--Joel<o:p></o:p>
<o:p> </o:p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
From: activepe=
rl-bounces [at] listserv.ActiveState.com [mailto:activeperl-bounces [at] listserv.Act=
iveState.com]
On Behalf Of Edward Peschko 
Sent: Wednesday, June 18, 2008 1:41 PM 
To: activeperl [at] listserv.activestate.com 
Subject: shared components in 'compiled' executables.<o:p></o:p></sp=
an>
</div>
<o:p> </o:p>
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) the 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<o:p></o:p>
<o:p> </o:p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"100%" align=3D"center">
</div>
This message may contain confidential or privileged information=
.. If you are not the intended recipient, please advise us immediately and d=
elete this message. See
http://www.datapipe.com/emaildisclaimer.aspx for further information on co=
nfidentiality and the risks of non-secure electronic communication. If you =
cannot access these links, please notify us by reply message and we will se=
nd the contents to you.<o:p></o:p>
</div>
</div>
 
<hr>
This message may contain co=
nfidential or privileged information. If you are not the intended recipient=
, please advise us immediately and delete this message. See http://www.data=
pipe.com/emaildisclaimer.aspx for further
information on confidentiality and the risks of non-secure electronic comm=
unication. If you cannot access these links, please notify us by reply mess=
age and we will send the contents to you. 

</body>
</html>

--_000_8964C02345560C4A8EE6A5F087387CD604C1A4BD4Eexchewr04da ta_--

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

_______________________________________________
ActivePerl mailing list
ActivePerl [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============0265125371==--