So the new commands I proposed for SWIG are:

Both are wrong ;)

When building a module, you're not building perl (like perlembed), so use a Makefile.PL

See perlxstut, h2xs, module-starter, ExtUtils::MakeMaker/Module::Build

Any thoughts? Could it be done better or differently?

If you insist invoking gcc yourself, don't assume everyone hash bash, just write a perl program to invoke gcc

system 'gcc', $ccflags, $in, $out ...;

In reply to Re: Updating broken and possibly incomplete SWIG Perl module building tutorial on SWIG web site by Anonymous Monk
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.