This is the mail archive of the 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]
Other format: [Raw text]

RE: GCC Include Paths

Vijay, Allan,

Cygwin is similarly limited. All Unix / POSIX systems have such a limit, but Cygwin's limit is much smaller than the typical limit on a Unix (-like) system. I don't know it for a fact, but I'm pretty sure this limit is not imposed by Cygwin itself (why would it?) but is a Windows limitation.

Most of the time "xargs" resolves this, but obviously that's not the case for -I arguments to gcc or in general when the argument overload originates in auxiliary arguments that name file system entities and which must all be present concurrently.

I suggest that you create a separate directory containing links (symbolic links or, if feasible (*), hard links) to all the (required) include files in all the include directories. Then you can side-step the argument list limit.

(*) Hard links are an option (the preferred option, actually) if the file systems are NTFS and the "target" of the link is on the same file system volume as the link. If the latter does not hold, Cygwin will copy the files, so this approach will still work, but you won't be using actual links. Lastly, in keeping with the pedantic theme of which I'm so fond, I put "target" in quotes since hard links are all co-equal and there is no "original" or "target" vs. "link" distinction, just alternate names for the same underlying file.

Good luck.

Randall Schulz
Mountain View, CA USA

At 10:29 2002-12-12, Vijay Sampath wrote:
Yes, we have faced a similar problem. The problem is with the windows
command shell which limits a line to 2048 characters. I don't know how
to make that problem go away. But you shouldn't get the same problem
from a cygwin shell.



> -----Original Message-----
> From: Allan Crook []
> Sent: Thursday, December 12, 2002 10:10 AM
> To:
> Subject: GCC Include Paths
> Help,
> We're trying to make GCC automatically search for required
> header files, unforunately if we use the C_INCLUDE_PATH
> environment variable or -I you need to enter every single
> search directory. For our current project this results in a
> line over 2000chars long (too long for windows or GCC to
> handle. Can we somehow tell GCC to search subfolders or is
> there some other way to do this???
> thanks,
> Allan.

Unsubscribe info:
Bug reporting:

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