hi I'd tested changing black slashes to singles quotes and different combinations, the result is the same, it did not throw any warnings about "unrecognised escapes" . i think the configuration is ok because it accept incpath. it knows where the cl.exe and D:\Perl\lib\CORE are. i'll install visual studio and inline again and test. thanks Migue ----- Original Message ----- From: "Sisyphus" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, April 27, 2002 5:27 PM Subject: Re: help please include with inline 0.43
> > ----- Original Message ----- > From: "Sam Tregar" <[EMAIL PROTECTED]> > To: "migu" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Saturday, April 27, 2002 12:50 PM > Subject: Re: help please include with inline 0.43 > > > > On Sat, 27 Apr 2002, migu wrote: > > > > > incpath='D:\Archivos de programa\Microsoft Visual > Studio\VC98\Include' > > > libpth=' "D:\Perl\lib\CORE" "D:\Archivos de programa\Microsoft > Visual Studio\VC98\lib"' > > > > Trying using paths without spaces. I wouldn't be surprised if that was a > > problem. > > > > -sam > > > > Yes - I, too, was thinking that could be the problem. > > If it is, then a simpler fix might be to enclose the incpath in double > quotes - which I think would mean that you would also have to change the > back slashes to double back slashes: > incpath="D:\\Archivos de programa\\Microsoft Visual > Studio\\VC98\\Include" > or, perhaps you could use a single forward slash: > incpath="D:/Archivos de programa/Microsoft Visual > Studio/VC98/Include" > > Then I noticed that libpth already uses double quotes and *single* > backslashes - which confuses me a little. Shouldn't that throw warnings > about "unrecognised escapes" ? > > Anyway, it won't take long to experiment with double quotes. > > Cheers, > Rob > >
