Hi Rich,
excactly that is what I need. This is my actual command line I currently testing:
ecc++.exe -v -I..\src -I..\src\public -target ppc-linux-eng -O3 -DGEN_TEST_DATA=1 -o test.bin @test.rsp
As far as I know from clang/llvm website, the content of @<file> should be converted to arguments.
(e.g. see: http://llvm.org/docs/CommandLine.html#response-files )
So for testing I put just the single string “make_no_sense” in my test.rsp and would expect some error ouput – alike what happend if I replace “@test.rsp” with “make_no_sense” in the command line … I got this:
ecc 0.1.27 based on clang version 3.8.0 (trunk) (based on LLVM 3.8.0svn)
Target: ppc-ellcc-linux
Thread model: posix
InstalledDir: C:\Tools\ellcc\bin
ecc++.exe: error: no such file or directory: ‘make_no_sense’
But using the first command line with @test.rsp it gives neither an error output nor an binary file.
In the files located in ellcc/libecc/config/ I haven’t found anything related to command line length.