Thanks for this. I like the idea of running a local CPAN repository to take care of hacks (and versions). I have a feeling I can do this so that the local repository just goes to a real one if it can't find what it's been asked to build. We could potentially then use a Module::Install script to make it easier to allow for a re-build for a new platform.
It still means I'd have to maintain a separate dir of built modules for each platform, but not sure there's an easy way around that.
In reply to Re^2: Dealing with XS modules on multiple platforms
by Mutant
in thread Dealing with XS modules on multiple platforms
by Mutant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |