If possible, I like to deal with portability issues in Makefile.PL so that
users have a smooth install experience. Here's how we're currently
configuring for Windows environments:
elsif ( $Config{osname} =~ m/^MSWin/ ) {
$cc_guess = 'cl -TP -EHsc';
$libs_guess = 'MSVCIRT.LIB';
}
Is there something smart we can do in the $cc_guess=.... line that would be
appropriate here?
On Sat, Mar 15, 2014 at 6:39 PM, <[email protected]> wrote:
>
> From: Dean Arnold
>
>
> which seemed to be solved by removing the "-nodefaultlib" link option. So
>> I copied the link command emitted by Inline::CPP and deleted that option
>> and reran the link, and it seems to work OK.
>>
>> Do you have any idea how I might be able to suppress that option in the
>> link commands emitted by Inline ?
>>
>
> You should be able to remove that option by rewriting lddlflags.
>
> On my machine I have:
>
> C:\>perl -V:lddlflags
> lddlflags='-dll -nologo -nodefaultlib -debug -opt:ref,icf -ltcg
> -libpath:"C:\_64\ap1600\lib\CORE"
> -machine:AMD64';
>
> If I wanted to remove the "-nodefaultlib" I would insert into the existing
> script:
>
> use Inline CPP => Config =>
> BUILD_NOISY => 1,
> LDDLFLAGS =>
> -dll -nologo -debug -opt:ref,icf -ltcg -libpath:"C:\_64\ap1600\lib\CORE"
> -machine:AMD64';
>
> The LDDLFLAGS config option might not be explicitly documented in the
> Inline::CPP docs
> (I haven't looked), but you'll find it documented in the Inline::C docs.
>
> The "BUILD_NOISY => 1," insertion is not part of the solution. It will
> enable you to see that the "-nodefaultlib" option is missing during the
> build process.
>
> Cheers,
> Rob
>
>
>
--
David Oswald
[email protected]
