Re^4: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker

The test in Inline::CPP.pm is

    my $iostream = "iostream";
#    $iostream .= ".h" unless $o->{ILSM}{STD_IOSTREAM};
    if($o->{ILSM}{MAKEFILE}{CC} =~ /^cl/) { 
        $iostream .= ".h" 
            unless $o->{ILSM}{STD_IOSTREAM}; 
    }
    $o->{ILSM}{AUTO_INCLUDE} =~ s|%iostream%|$iostream|g;
[download]

Ie. If the compiler command is 'cl' append '.h'. But, according to MS, all their compilers since VS 2003 now only supply the newer standard extension-less standard header files.

I have Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64 which I memory serves equates to VS 2008; internal version 9; File format version 10. (Damn I wish they'd use ONE bloody name for things!), so I think the above test will need to be more selective.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Re^4: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker Select or Download Code

Replies are listed 'Best First'.
Re^5: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker by davido (Cardinal) on Dec 15, 2011 at 20:05 UTC
Thanks again. I'm thinking that this may better be handled by `#ifdef` segments, as surely I should be able to find some examples of robust solutions implementing that approach. So far, however, I seem to not be using search terms that land me on anything useful. Dave	[reply] [d/l]
Re^6: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker by BrowserUk (Patriarch) on Dec 15, 2011 at 21:08 UTC
I suspect that this might do the trick: `_MSC_VER Reports the major and minor versions of the compiler. For example, 1310 for Microsoft Visual C++ .NET 2003. 1310 represents +version 13 and a 1.0 point release. The Visual C++ 2005 compiler version is 1400. In Visual Studio 2008, _MSC_VER is defined as 1500. The Visual Studio 2010, _MSC_VER is defined as 1600.` [download] Anything less than 1300 and you add the '.h', otherwise leave it off. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply] [d/l]
Re^7: (solved) Clean smoke-test install for Inline based modules using Inline::MakeMaker by davido (Cardinal) on Dec 15, 2011 at 21:19 UTC
Perfect. ...Now for a free hour to apply and test a patch... I'll follow-up to your latest reply in this subthread once I get a chance to put a new version of Inline::CPP (v0.34 probably) on CPAN. Probably by tomorrow PST. I've got three other "FAIL"'s that I'm trying to work out in that module as well. One seems to be a linker issue, as the smoke tester's error message has mangled function names (name mangling is typical of C++) which show in the error message (undesirable, and atypical for C++. lol). Dave	[reply]