 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / Perl / February 2007ANNOUNCE: Perl Dev Kit 7.0 Beta 2 available
I'm happy to announce the release of the Perl Dev Kit 7.0 Beta 2. http://www.activestate.com/products/perl_dev_kit/beta.plex If you never heard of the Perl Dev Kit before: ActiveState Perl Dev Kit (PDK) is a suite of tools for rapidly developing and delivering Perl applications. It includes everything you need to turn Perl programs into ready-to-run executables, debug Perl scripts, generate code for sophisticated filters, convert useful VBScript code to Perl, and create .NET and ActiveX components, Windows services and system tray applications. The PDK is commercial software. You will need to purchase a license for PDK 7.0 to continue to use it after the beta period. This release extends the beta expiration period to March 20th 2007. There are only minimal functional changes relative to Beta 1. The purpose of the Beta program is to receive feedback on new features. If you decide to try out the PDK 7 beta then please also subscribe to the PDK-beta mailing list to discuss the beta with both ActiveState and other beta tester. In addition you can always file bugs and enhancement requests at http://bugs.ActiveState.com Major changes since PDK 6 are: * Coverage and Hotspot Analyzer Analyze code coverage and hotspots in Perl programs and test suites. Test different versions or revisions of a program and compare them visually, or compare different test runs on the same code. * Mac OS X Support PerlApp, Filter Builder and the new Coverage and Hotspot Analyzer are now available for Mac OS X (Universal). * 64-Bit Support 64-bit command line versions of PerlApp are available for Linux (x86_64), Solaris (Sparc) and Windows (x64). 64-bit command line versions of PerlCtrl, PerlSvc and PerlTray are also included in the Windows builds. * Improved 32-Bit Support The GUI interface to PerlApp, Filter Builder, and the Coverage and Hotspot Analyzer are available for Solaris 10 on Intel (x86) and AIX 5.x. The command line version of PerlApp is available for HP-UX on Itanium. * Visual Package Manager (VPM) VPM has been superseded by the native PPM4 GUI included in ActivePerl 819 and later. This beta release can be installed side-by-side with the PDK 6 release version as long as it's installed in a separate directory. The installer does this by default. Cheers, -Jan > I'm happy to announce the release of the Perl Dev Kit 7.0 Beta 2. > > http://www.activestate.com/products/perl_dev_kit/beta.plex > > ... seems attractive but : System Requirements * Mac OS X 10.4 "Tiger" or later * ActivePerl build 816 or later <<--  Signatureklp On 2 feb 2007, at 19.06, kurtz le pirate wrote: >> I'm happy to announce the release of the Perl Dev Kit 7.0 Beta 2. >> [quoted text clipped - 9 lines] > -- > klp So what? ActiveState Prel for Mac OS X is easy to download. It installs in a subdirectory of /usr/local, so it won't overwrite the existing Apple-built perl. ------------------------------------------------------ "Home is not where you are born, but where your heart finds peace" - Tommy Nordgren, "The dying old crone" tommy.nordgren@chello.se On Fri, 02 Feb 2007 19:06:10 +0100, kurtz le pirate <kurtzlepirate@yahoo.fr> wrote: >> I'm happy to announce the release of the Perl Dev Kit 7.0 Beta 2. >> [quoted text clipped - 3 lines] >System Requirements > * Mac OS X 10.4 "Tiger" or later The final release will support 10.3.9 or later. But the current releases have a problem with the Apple installer stripping additional information from executables and libraries during installation, turning Universal binaries into PowerPC binaries during the install. We do have a workaround for that. > * ActivePerl build 816 or later <<-- I assume you are objecting to the requirement of ActivePerl itself, and not that you need build 816 or later. I think ActivePerl is really only "required" for the PerlApp program; both the Filter Builder and the Code Coverage tool should work with the Apple Perl. The reason PerlApp requires ActivePerl is that we made a few changes to the way it is build that makes it more robust to embed it in other applications. One example is that the DynaLoader code in ActivePerl is in the libperl.dylib and not in the perl executable itself. That means that the embedding application isn't restricted to one specific version of DynaLoader, but could work with an updated DynaLoader as long as it also uses the updated libperl.dylib. Technically even PerlApp works with the Apple Perl, because the PDK includes a copy of libperl.dylib from ActivePerl for its own use, and will use this libperl.dylib if the Perl you are using is not ActivePerl. Note that installing ActivePerl on OS X doesn't replace the Apple Perl installation; it installs into /usr/local/ActivePerl-5.8 and can also be removed without affecting any other part of the system using Apple Perl. Cheers, -Jan quoth Jan Dubois: > quoth kurtz le pirate: > > quoth Jan Dubois: > > > I'm happy to announce the release of the Perl Dev > > > Kit 7.0 Beta 2. > > > http://www.activestate.com/products/perl_dev_kit/beta.plex > > seems attractive but : > > System Requirements [quoted text clipped - 4 lines] > ActivePerl itself, and not that you need build 816 > or later. I think ActivePerl is really only "required" > for the PerlApp program; both the Filter Builder > and the Code Coverage tool should work with the > Apple Perl. If I had to guess, the objection may be to requiring ActivePerl itself, not in opposition to Apple's Perl specifically, but in opposition to any other Perl. A number of people on this list have traditional `./configure && make && make install` Perls or Fink Perls installed and configured for their needs. Live well, ~wren ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 On Fri, 2 Feb 2007 16:01:19 -0800 (PST), wren ng thornton <phreelance@yahoo.com> wrote: >If I had to guess, the objection may be to requiring >ActivePerl itself, not in opposition to Apple's Perl >specifically, but in opposition to any other Perl. A >number of people on this list have traditional >`./configure && make && make install` Perls or Fink >Perls installed and configured for their needs. I understand, but this is in general not possible. The Perl Dev Kit contains C code that embeds the Perl interpreter, or provides XS functionality. All this code must be compiled with the same build options as the version of Perl you are going to use it with. You run into the same problem if you compile Perl yourself e.g. without thread support, and then expect that modules from the Apple Perl tree will work with your Perl. They won't; you will have to recompile those modules with your Perl too, so that the XS code gets compiled with the correct options. As I hinted at in my previous message, if you compiled your Perl with the same options as ActivePerl (which uses the same options as Apple Perl), then things will most likely work. But from a support point of view, we have to say: any problem that cannot be reproduced with ActivePerl will not be treated as a Perl Dev Kit bug but as a local configuration problem. Essentially: If you know what you are doing, then you can probably get most stuff working with your own Perl. But if you don't understand why something breaks, when it breaks, then you are better of using the "supported combination" of ActivePerl and the Perl Dev Kit. Cheers, -Jan > quoth Jan Dubois: > > quoth kurtz le pirate: [quoted text clipped - 25 lines] > `./configure && make && make install` Perls or Fink > Perls installed and configured for their needs. yes, not activeperl itself, not build xxx... i work with v5.8.8 on 10.3.9. the latest version of perl that i have installed, compiled and configured for panther on /usr/local/bin/perl. standard perl on panther is 5.8.1 on /usr/bin/perl so, activeperl it's just an OTHER perl ! Signatureklp > On Fri, 02 Feb 2007 19:06:10 +0100, kurtz le pirate > <kurtzlepirate@yahoo.fr> wrote: [quoted text clipped - 38 lines] > Cheers, > -Jan I do not find that objectionable. It would be nice to be able to use "Perl" but the Dev Kit is your application and you should get to set the parameters of its usage. Robert |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.