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?

the order is determined by Inline::CPP when it creates the XS file in folder _Inline/build. Perl headers come first

Inline::C has the PRE_HEAD Config option that enables one to place the code of one's choice *before* the perl headers. I haven't specifically checked, but I would expect the PRE_HEAD option works also with Inline::CPP.

Cheers,
Rob

but how that would work with the headers in the __CPP__ section? Must I remove the headers from the __CPP__ section and add them to the pre_head string?