On Sat, Feb 13, 2010 at 09:16:44PM +, Alberto Simões wrote:
> My main problem is that I lack knowledge on building the xs code myself.
Take a look at the ACTION_compile_custom_xs method. It's basically a manual
override for compiling and linking a multi-module C library into a single XS
shar
# from Marvin Humphrey
# on Saturday 13 February 2010 13:12:
>> But if I want to use c_source or xs_files and the build for these
>> elements depend on a build element, how can I force the order?
>
>Use Module::build's actions.
>
> sub ACTION_code {
> my $self = shift;
> $self->
Hey, Marvin
Thanks for your link. I think it might get handy.
My main problem is that I lack knowledge on building the xs code myself.
With luck I can take same of your code and learn...
Thanks
Alberto
On 13/02/2010 21:12, Marvin Humphrey wrote:
> On Sat, Feb 13, 2010 at 08:26:36PM +, Albert
On Sat, Feb 13, 2010 at 08:26:36PM +, Alberto Simões wrote:
> But if I want to use c_source or xs_files and the build for these
> elements depend on a build element, how can I force the order?
Use Module::build's actions.
sub ACTION_code {
my $self = shift;
$self->dispa
Hi
As far as I could find out, add_build_elements add a build element to an
array or so, and that order is maintained.
But if I want to use c_source or xs_files and the build for these
elements depend on a build element, how can I force the order?
Thank you
Alberto
--
Alberto Simões
