On Wed, 4 Mar 2009, Zefram wrote about _cbuilder as build param:
...
For a workaround in my code, it's clear that remedially loading EU:CB
isn't going to be enough, wherever I put it. (Wrapping ->cbuilder would
be cleaner than the current hack in ->find_xs_files, but ineffective
on Windows.) Mr Golden suggested (based on empirical work) that I test
for the availability of C building facilities by attempting to load
ExtUtils::CBuilder myself, rather than by calling $self->cbuilder. This
obviously works by avoiding creating a cbuilder early enough to get into
_build/build_params. I'm dubious about it, though. I don't care about
the availability of EU:CB myself; it is neither necessary nor sufficient.
I care, precisely, about whether M:B is offering C building facilities.
The other option that I see is to delete $self->{properties}->{_cbuilder}
at some opportune moment, possibly by wrapping ->write_config.
I would have tried a hackish fix (and still might, for backwards versions
of M::B):
1: Checking if @EU::CB::Platform::Windows::ISA has the subclass that
EU::CB::Platform::Windows puts there, and save it where I could pick it up
again.
2: Fudging @EU::CB::P::W::ISA by pushing the saved value back on upon
reloading.
If too tough or too ugly, take the easy way out: Require M::B 0.33 or so,
assuming it would have the patch previously mentioned! :)
--Curtis
--
Curtis Jewell (Perl-programming e-mail)
[email protected]
[email protected] http://curtis.livejournal.com/
Your random numbers are not that random
--perl5.8.8/util.c
[I use PC-Alpine, which deliberately does not display colors and pictures
in HTML mail]
