This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: INCLUDE_PATH


Mike MacDonald <mmacdona@tsi.gte.com> writes:
> Is there a way to set an include path, or an ld_library_path?  Do these
> things work in cygwin?

Please see the GCC documentation. If you're using GNU info reader:
  
   $ info gcc invoking environment

If using HTML docs, look for "Invoking GCC" at top level and then 
"Environment Variables affecting GCC" section.

In general, if the manual says something works, it works; if you find 
that it doesn't, it's a bug, and report it to gcc-bugs@gcc.gnu.org.

Just try it out, it's not that hard.
  
  $ cd /tmp
  $ cat > foo.h
  /* empty file. */
  ^D
  $ cat > foo.c
  #include <foo.h>
  int main () { return 0; }
  ^D
  $ export C_INCLUDE_PATH=`pwd`
  $ gcc -c -v foo.c

ld_library_path? I assume you mean LD_LIBRARY_PATH, which is a runtime
loader option, and has nothing to do with GCC. If you use dlopen() and
friends to access DLLs in Cygwin, Cygwin will use LD_LIBRARY_PATH to
find the DLL to be loaded.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]