We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There already is a TODO in msvc.rs mentioning this, but I think it is good to have an issue open for better visibility.
msvc.rs
It seems quite straight-forward to add support for options starting with / as well.
/
See: https://msdn.microsoft.com/en-us/library/610ecb4h.aspx
Options are specified by either a forward slash (/) or a dash (–).
Additionally, it might be good to also support options that accept arguments after a space.
If an option takes an argument, the option's description documents whether a space is allowed between the option and the arguments
For example, I have encountered defines being set like /D WIN32 instead of /DWIN32. Maybe this should have a separate issue.
/D WIN32
/DWIN32
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There already is a TODO in
msvc.rs
mentioning this, but I think it is good to have an issue open for better visibility.It seems quite straight-forward to add support for options starting with
/
as well.See: https://msdn.microsoft.com/en-us/library/610ecb4h.aspx
Additionally, it might be good to also support options that accept arguments after a space.
For example, I have encountered defines being set like
/D WIN32
instead of/DWIN32
. Maybe this should have a separate issue.The text was updated successfully, but these errors were encountered: