Hmm, on further inspection, it's not quite as simple as that, and I'm still confused. When I execute:
perl Makefile.PL make make test make dist
I get no such warning at any stage in the process. How is it that the target in some cases is coming up with that warning?
In fact, when I examine the META.* files I see that the build requirement is getting listed therein when I make dist. So I'm still bewildered.
I'm learning here too, and the whole concept of basing a module on Inline seems to be a road less traveled. In fact there are tools to automate the process of converting an Inline extension to plain old XS for the purposes of distribution. So this isn't really a critical adventure. But if we're not too far away from making Inline based modules distributable I'd like to see it through.
ExtUtils::MakeMaker is always somewhat of a quagmire. I suspect even more-so when we're dealing with Inline::MakeMaker. But it seems like the goal isn't that far away.
If I haven't said so before, thanks for your reply both here and to the many other threads where I've learned something from your answers.
Dave
In reply to Re^2: Clean smoke-test install for Inline based modules using Inline::MakeMaker
by davido
in thread Clean smoke-test install for Inline based modules using Inline::MakeMaker
by davido
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |