Include and lib search paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: gcc-help@xxxxxxxxxxx
- Subject: Include and lib search paths
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Date: Sat, 20 Jun 2015 12:30:37 -0400
- Authentication-results: sourceware.org; auth=none
- User-agent: Mozilla/5.0 (Windows NT 6.0; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
I use both Windows and Linux. On Windows when using mingw or mingw-64 I
noticed that the search paths for include directories and lib
directories were hardcoded to c:\mingw. This fact makes it much harder
to run multiple versions of gcc on Windows. When I asked why absolute
hardcoded paths were used instead of relative paths to the gcc
installation I was told this was because gcc itself did it this way.
So now I ask here. Why does gcc use hardcoded absolute paths to include
and lib directories when relative paths within a gcc installation would
make gcc much more portable and would make it much easier for multiple
versions of gcc to co-exist ?
[Index of Archives]
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]