Kenneth Ölwing <[EMAIL PROTECTED]> writes: > My objective is to use ActivePerl+PerlApp to build an app from Perl source > in at least three flavors (Windows, Linux, Solaris). > > On the theory that I'd like to keep strict control on configurations, and > that 'less redundancy is better', Ideally, I'd like it all to reside in CM > controlled space - i.e. 1) an ActivePerl for each platform, 2) a PerlApp for > each platform, 3) a single PERLLIB area (for all the modules I expect to > download and install) and 4) our own source code. > > Beginning from the back, #4 is a no-brainer of course. Leaving #3 for a > second, I believe #1 and #2 is simply to messy to handle this way. If anyone > has information to the contrary, I'd be interested to hear about it, > especially how to deal with the issue of things in the AP tree having > hardcoded paths to the installation (as this will be incorrect using a CM > system where the tree can be checked out anywhere). Also, would it be > possible/easy to factor out just the differences between the things?
A suggestion: You could check in the *.tar.gz (or .zip for Windows) files for the ActivePerl and PDK distributions you want to use into your CM system and then just have scripts install them to a temporary location each time you want to build something with this perl. This shows how ActivePerl could be installed and run from a script: PERLDIR=/tmp/build-$$ tar xzf ActivePerl-5.8.8.819-i686-linux-glibc-2.2.4-gcc-267479.tar.gz cd ActivePerl-5.8.8.819-i686-linux-glibc-2.2.4-gcc-267479 ./install.sh --prefix=$PERLDIR --license-accepted --no-install-html cd .. rm -rf ActivePerl-5.8.8.819-i686-linux-glibc-2.2.4-gcc-267479 $PERLDIR/bin/perl -v rm -rf $PERLDIR > On #3 however, I wish to confirm that I have understood it correctly that a > single tree can be shared. As I've understood it, this will work due to 1) > most modules are just plain text files anyway, and 2) modules that need > binaries will have their stuff installed in separate dirs by platform. > Correct? ActivePerl does not use platform specific subdirs for the perl modules so 2) does not hold. You would need to create separate trees for each platform. Regards, Gisle Aas, ActiveState _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
