Add support for "reponse files" to workaround Windows command line length limitations
I have a program (git-annex) which builds successfully on windows, but when I enable any of three optional features which pull in some additional libraries, it fails to link.
I will attach the output of cabal build --ghc-options=-v for a failing and a successful build.
I hypothesize this is due to a command line length limit. The final failing gcc link command is 43814 characters, vs 30765 in the configuration that succeeds. Right around the 32k boundry.
Not sure what I can do to work around this, short of splitting up my program into standalone libraries which will link without referencing every individual module?