So what's the good way to generate XS (automatically) for access to a large source distribution?

I don't know - it's not something I've done, and Example 4 would indicate that a large amount of hand-editing of the XS file that's generated by h2xs would be required.
However, you might find something useful in perldoc Inline::C::Cookbook.
For example there's a small section headed "Replacing h2xs" that seems to discuss this very issue, though it's thin on detail and I don't understand it.

FAIRK, maybe that fiddly "Example 4" is, in fact, as good a way as any ?

Cheers,
Rob

In reply to Re^3: some questions about example 4 of perlxstut by syphilis
in thread some questions about example 4 of perlxstut by Anonymous Monk

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.