From: Chris T. <ch...@lu...> - 2002-12-11 03:36:48
|
I created a my_include.h w/ a simple #define in it at /home/unknown and compiled source that relied on the header at /home/unknown/src. It compiled successfully using gcc my_source.c -o my_source -I../. A relative include works. I then tried an absolute include of -I/home/unknown/ and it did not work. I tried using sdl-config (installed correctly) and it passes a compiler flag for the preprocessor include as an absolute directory, /usr/local/cross-tools/... which does not work. However, using a relative include myself, ../../usr/local/cross-tools/... works correctly. Is there a bug in mingw's gcc when it comes to accepting absolute preprocessor directories? This is all under cygwin btw, which might be the cause. Any thoughts? On Sun, 2002-12-08 at 20:00, Oscar Fuentes wrote: > Chris Thielen <ch...@lu...> writes: > > > Hello, > > Sorry if this is documented but does mingw's gcc not support > > -I for preprocessor include directories? I have code that refers to > > "my_include.h", stored in the parent directory, and unlike gcc on > > Linux, I cannot simply say -I../. Is this a bug in mingw? > > It should work. Try with -I../ or -I.. -- Chris Thielen <ch...@lu...> |