On Sun Aug 21 09:48:30 2016, bubnikv@gmail.com wrote: > Hello. > > I am trying to set up a development perl environment compiled from scratch > with Visual Studio 2013 free C/C++ compiler. I stumbled over a following > problem: > > If the XS file contains an INCLUDE_COMMAND call, this line is later stored > as a comment into the generated XS.c file in a form of #line NUMBER > "filepath". Here the "filepath" will be the complete parameter of > INCLUDE_COMMAND. If the parameter contains escaped quotes, this breaks the > __FILE__ substitution in the visual studio C++ compiler. > > Here is an example of a #line inserted into XS.c, which the Visual Studio > C++ has a problem with: > > #line 112 "c:\\\\wperl64d\\\\bin\\\\perl.exe -MExtUtils::XSpp::Cmd -e xspp > -- -t \"D:/src-perl/Slic3r/xs/xsp/typemap.xspt\" > \"D:/src-perl/Slic3r/xs/xsp/Print.xsp\"" > > If I remove the quotes from the INCLUDE_COMMAND call, the resulting form is > swallowed by the Visual Studio compiler without any problem. How exactly does it fail? What error message does it produce? -- Father Chrysostomos --- via perlbug: queue: perl5 status: new https://rt.perl.org/Ticket/Display.html?id=129035Thread Previous