-
Notifications
You must be signed in to change notification settings - Fork 790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for response file to fsc #816
Comments
👍 |
Yes, this is a long time missing feature from F#, I have been figuring I would add it at some point, however, nothing fails to work because it is missing, so it has seemed like a very low priority feature to me. I would certainly eagerly consider accepting a PR for this feature. |
i'll try to add it, it's really useful for dotnet cli development. About this feature, I'll start with |
I've encountered response files in the past and it was always using https://gcc.gnu.org/wiki/Response_Files I'd vouch to keep the same convention as others compilers, especially if roslyn uses the same. |
ah nice @smoothdeveloper , good that is a shared command line option, thx for feedback llvm too http://llvm.org/docs/CommandLine.html#response-files nice. no more open questions so 😄 |
Fixed in #831 |
like roslyn. it's not because is roslyn, i think is useful
add
@file
argument tofsc
ref https://msdn.microsoft.com/en-us/library/8a1fs1tb.aspx
Long story short:
A file that lists compiler options or source code files to compile, instead of pass compiler arguments.
Goodies:
it's nice to have a base configuration, and two files, for example debug, test or perf as additional
more easy to track in source control ( it's a text file ) instead of concat argument list in script
The text was updated successfully, but these errors were encountered: