<div class="gmail_quote">On Thu, May 21, 2009 at 4:29 PM, Brian Manning <span dir="ltr"><<a href="mailto:elspicyjack@gmail.com" target="_blank">elspicyjack@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Thu, May 21, 2009 at 4:03 PM, Bob Forgey<<a href="mailto:rforgey@alumni.caltech.edu" target="_blank">rforgey@alumni.caltech.edu</a>> wrote:<br>
> Can I use Camelbox and PAR to package up a Perl application as a<br>
> single executable for Windows? If my app is GPL, does Camelbox's<br>
> license allow this? It's my understanding that Activestate's license<br>
> doesn't.<br>
<br>
</div>That's not how I'm reading their license [1]. In any case, Camelbox<br>
is licensed under the same terms as Perl itself (Perl Artistic *or*<br>
GPLv1).<br>
<br>
Camelbox does come with PAR, however, PAR is not "perfect", meaning<br>
I've yet to come up with a workable solution for wrapping anything<br>
having to do with Gtk2-Perl. The PAR FAQ goes into this a little bit<br>
[2]. My experience has been that PAR picks up Gtk2-Perl .dll<br>
libraries, but it fails to map them correctly back to their original<br>
filenames when they're unpacked in order to run them. Other modules<br>
that use straight XS calls and pure-Perl modules should work fine<br>
using PAR on Windows.<br>
</blockquote><div><br>OK, I guess it's a good idea to read these things carefully and<br>completely! I'm still very glad to hear about Camelbox, though; it<br>will be very nice to just be able to use CPAN, and not to also have to<br>
deal with ActiveState's PPM.<br><br>Thanks again,<br>Bob<br><br></div></div>