The source isn't necessary as long as you can link to the library files (.dll or .so). However, from the example you give, you might have some work ahead of you, depending on how complicated XFortCreatePAReqResult is. My best advice is to copy+paste shamelessly from existing Perl C++/XS projects, for example http://search.cpan.org/dist/Lucene/ or http://search.cpan.org/dist/Wx/ (I also have two, http://search.cpan.org/dist/Mozilla-DOM/ and http://search.cpan.org/dist/Ogre/, but I don't necessarily recommend them as good examples... :) ).

By the way, I'm interested in knowing what other examples of C++ libraries there are (edit: sorry, I meant C++ libraries with Perl XS bindings), or ways of finding out. Also I'm interested in someone porting Py++ to Perl/XS.

In reply to Re: Integrating ePDQ C++ library using PerlXS by ForgotPasswordAgain
in thread Integrating ePDQ C++ library using PerlXS by weboutreach

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.