I explained that this is for compiling a SWIG auto-generated XS and .pm binding code for specified C code, so it makes no sense to have to go through the additional hassle of creating and using a Makefile.PL when all you need are the gcc compile and gcc link commands that should be used for building a Perl module. ExtUtils::MakeMaker and Module::Build get the same gcc compile and gcc link flags from Perl core Config.pm no? They just put it into a Makefile as constants and during make they through them into the gcc compile and gcc link commands. I am doing the same but just shortcutting the parts I don't need.

The commands I provided produce the same gcc compile and link commands that you see when you install a CPAN module with C/C++ w/ XS code so how can this be wrong? Please check for yourself. The only flags that are excluded are not relevant to a SWIG Perl module build. CPAN modules with C/C++ w/ XS code are compiled like Perl itself was and should be, I don't know here if there is a misunderstanding here.

In reply to Re^2: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site by hermida
in thread Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site by hermida

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.