It's generally speaking more convenient to use / instead of .
/ Per Hedbor ()
Previous text:
2004-01-06 16:23: Subject: Re: #include
do backslashes need to be escaped? (ie \ should be \)? I've not got too much experience on the windows platform, but this might be the problem.
Bill
On Tue, 6 Jan 2004, Credence Shanden wrote:
Actually I have been using. #include "absolute filepath" . I have not enclosed the filename with <>'s since the -I command crashed pike through the command prompt. (FYI I am using Windows XP). As for the poster's original question, I think that perhaps the include path might be incorrect. Try adding the path the include files are in with a -I command argument. That assumes you're using #include <includefile.h>
Bill
Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
/ Brevbäraren