Re^2: Dealing with XS modules on multiple platforms

Hi. Thanks, but I'm not sure this really solves my problem. Deploying the modules is not an issue (I don't mind where they're deployed, the Perl code using them can just include the right path). I just want an easy way of building them for each platform with as little overhead and chance of making mistakes as possible.

I'd also like to avoid building things as they're deployed. This can solve some of the issues, but it introduces another thing that can go wrong in the deployment process.

Comment on Re^2: Dealing with XS modules on multiple platforms

Replies are listed 'Best First'.

Re^3: Dealing with XS modules on multiple platforms
by Bloodnok (Vicar) on Jul 24, 2008 at 12:43 UTC

If my suggestion is, at least in part, acceptable, the deployment is restricted to once per platform flavour ... c/w once per consumer/user.

The suggestion regarding the common includeable make(1) script presumes that the same build standard is required on all platform flavours.

If the standard make test install fails, then you've probably got bigger worries. Note also that, without intending to be offensive, it almost sounds like you aren't aware that...

the test target causes a build of the whole module - including any XS elements.
the install target is attempted iff the test succeeds.

Hope that clarifies things (a bit) ,

At last, a user level that overstates my experience :-))

[reply]
[d/l]
[select]


We don't bite newbies here... much
	PerlMonks