This relates to Inline::Module based distributions written with Inline::CPP.

Inline::CPP configures platform dependent details at install time. Currently when we bundle Inline::CPP with our distributions, we're bundling the configuration as it stands on the author's system. This configuration is generated by Inline::CPP's Makefile.PL. Inline::CPP::Config is where the configuration details reside; it's generated.

We need to make sure that end users are getting a configuration that works for their system. This can probably be done by getting Inline::CPP to delay its configuration, or to re-configure upon deployment to an end user system in the context of an Inline::Module distribution.

Also, Inline::CPP's configuration depends on ExtUtils::CppGuess (non-core), which depends on Capture::Tiny (non-core). Additionally, the configuration phase depends on two private modules bundled in the Inline::CPP distribution's inc/.

Probably what has to happen for Inline::Module dists that use Inline::CPP is to bundle all Inline::CPP dependencies (including those that are part of IL::CPP's inc/ folder already), and then set up a configuration phase at target module build time.