Thanks for the idea but the order is determined by Inline::CPP when it creates the XS file in folder _Inline/build. Perl headers come first. However I did change the order of the includes manually (e.g. without re-perling, I went into said folder and edited the XS file). The first error (seed redefined) is gone (something tells me it will reappear if/when I make Perl call its seed) but the second error (e.g. namespace cv clashes with struct cv) persists (obviously).

My knowledge of XS is zero, but wouldn't using XS/XSpp require including those OpenCV headers? And still get the clash with Perl's headers?

In reply to Re^3: Inline::CPP + OpenCV = problems by bliako
in thread Inline::CPP + OpenCV = problems by bliako

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.