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
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 10:10 AM
To: [EMAIL PROTECTED]
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
PROTECTED]
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
, December 12, 2002 10:43 AM
To: [EMAIL PROTECTED]
Subject: 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
Vijay,
I guess I was misled by this:
/usr/include/limits.h:#define _POSIX_ARG_MAX 4096
/usr/include/sys/syslimits.h:#define ARG_MAX 65536 /* max bytes for an exec
function */
Furthermore, /usr/include/limits.h bears a Red Hat copyright and is
specifically marked as a part of Cygwin, while
Vijay Sampath wrote:
I just tried out a line with 2 characters and it works fine on bash
as an input to GCC.
I think that direct Cygwin-to-Cygwin invocation has a higher limit. If
you're calling a Cygwin program from a non-Cygwin program (e.g.
CMD.EXE), you're still stuck with Windows
6 matches
Mail list logo
