In another thread, the recommendation to build perl modules (e.g., PDL) *not* using the system perl came up again.
My experience is that for maximum portability and testability you usually want to build against the "official OS perl" in the "official OS location". That way other users and developers can reproduce your build environment which is needed to diagnose and fix bugs. In addition, while building one's own perl is relatively straightforward, it is not something we should be recommending to PDL beginners nor is it something that should be required for PDL development. For cygwin development, I've been successful with maintaining a personal module tree built using the system perl. Is this recommendation based on the limitations of the Mac OS X platform (I thought it was pretty much unix) or is this something other users and developers should be recommended to do? Cheers, Chris On 9/9/2010 10:12 PM, Tim Jenness wrote: > > It's not recommended to build modules using the system > Perl since Apple might change it at any time > (and you have to be careful to install the files > somewhere outside of /System or /Library). > It's always easier to build your own perl in /usr/local > or even your home tree. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
