OK Brett and all,
I've been to hell and back. I've faced the depths of MakeMaker so that
no Inline user need ever fear it again.
This was very subtle code, but I think I've nailed it. I was quite naive
going into this. I'm glad Brett had a big project to put
Inline::MakeMaker to the test. I had to patch Inline.pm as well. Best of
all, the Makefile.PL rules are simple again. Here they are:
For directories with no Inline code, use a regular Makefile.PL. That is,
'use ExtUtils::MakeMaker'.
For directories *with* Inline code, use 'use Inline::MakeMaker' *and*
change 'WriteMakefile' to 'WriteInlineMakefile'.
This is my safety check. I could have continued to substitute my
'WriteMakefile' for the real one, but I've decided there's no point. It
will just cause confusion in the long term. ExtUtils and Inline are now
mutually exclusive in this regard.
I still need to test this patch and a couple others on multiple
platforms. I'll do that later this weekend, and put
Inline-0.41-TRIAL1.tar.gz out on inline.perl.org. Stay tuned...
Cheers, Brian
PS I'll also post my modified version of Brett's test case. One
(important) thing the test did not address was an Inline directory under
another directory. Inline::MakeMaker handles this now.
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
