Prof. A Olowofoyeku (The African Chief) wrote:
On 18 Sep 2002 at 9:21, I wrote:
On 18 Sep 2002 at 0:57, Frank Heckenbach wrote:
[...]
But something else (I still don't really understand the story): Searching of gpcpp does not use the unit-path. The path is hard-coded while building GPC, so if it is installed in the same directory, no option is needed to find it. Otherwise it can be set with a `-B' option or an environment variable GPC_EXEC_PREFIX. Is that what the IDE sets for the "bin directory"?
This is an example of output of the "compile log" window: "c:\dev_gpc\bin\gpc --automake c:\dev_gpc\examples\untitled1.pas -oc:\dev_gpc\examples\untitled1.exe -fno-inline -fno-io-checking -fno-stack-checking -O1 -march=i386 -mcpu=i386 -funit-path=c:\dev_gpc\units -Bc:\dev_gpc\lib\ -Bc:\dev_gpc\lib\gcc- lib\ -Bc:\dev_gpc\bin"
So the necessary "-B" switches are there - and I cannot see why there should be a problem.
I have now checked the compile log again, and I can see that the entire command line contains about 273 characters. Perhaps we have come across a DOS limitation here? I seem to remember that DOS (or command.com) has some limits in respect of how long a command line can be (128 characters?). If this is the problem, then I don't know what one can do about it.
I don't suppose it's that, since Maurice said that omitting the `c:' helps. That certainly doesn't bring the length below 128. ;-)
I know that DJGPP uses some ways around this limit when one DJGPP program calls another one. I don't know if/what mingw does, or if the limit exists at all under Windows. Someone might want to try it, but I guess if the limit really applied, this would have been noticed much earlier.
Frank