-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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 an output path in mono-api-diff #9556
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be explicit option. e.g. -out:File
This makes it a bit harder as we will have to move the files around and add a reference to mono.options… Right now this folder is all set up to build mono-api-info.exe. This appears to be just a single file. Is that an option? |
I'd love for the mono-api-info.exe to follow the standard mcs/tools setup we have everywhere else |
let me get on it then :) |
@marek-safar I moved the mono-api-diff tool into its own folder: #9563 |
Rather than always writing to the std out, provide an option to write to a file. This makes things easier for tooling but not requiring RedirectStandardOutput = true
Rather than always writing to the std out, provide an ability to write to a file using the `-o=<file>` or `--output=<file>` option. This makes things easier for tooling by not requiring RedirectStandardOutput = true
…r `--output` for consistency with existing tools
I think this is ready to be merged from my side. I tested the app with my projects, and it works as expected. |
@monojenkins build failed |
Rather than always writing to the std out, provide an option to write to a file. This makes things easier for tooling by not requiring
RedirectStandardOutput = true