-
Notifications
You must be signed in to change notification settings - Fork 562
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
Support building DR with VS2015 #2166
Comments
#2125 is about building a client, not DR. I don't think anybody has tried building DR itself with VS2015. This issue will cover that support. It is not unusual for new compiler versions to have a few new warnings. If you end up with a patch to fix the warnings please contribute it back upstream. |
Ah okay that was my mistake. I'll keep poking around and if I can come up with a fix then I'll submit a pull request :) Edit: There are also errors within the build process which is why I'm currently halted but I'll keep working on this. |
This should be fixed by linking against 'legacy_stdio_definitions.lib'. Cheers |
The WinAFL project had the same issue which was resolved with the following PR: https://github.com/ivanfratric/winafl/pull/46 I added the following libraries to the project: |
Sounds right, that is what was added to clients in 94aeb0e Just be careful that some core libraries need to have zero libc-ish dependencies so we cannot have dynamorio.dll itself importing from any dll other than ntdll.dll. |
Thanks for the heads up! I'll be able to do some troubleshooting and such tonight. I'll posts any edits in this thread before submitting any PRs |
We can add a VS2015 build to Appveyor once it's working. Unfortunately Appveyor, unlike Travis, doesn't run build jobs in parallel, so it will add to the total time: but in the middle of weekdays we're waiting for Travis Mac VM contention anyway. |
Xref #1902 |
Hi @b1ack0wl, did you end up fixing it? Thank you |
We are adopting VS2017 as the officially supported build. We would expect VS2015 to work as well but there is no planned effort to test it or maintain it. Closing. Of course if someone wants to support it and add a Jenkins build to maintain it that is certainly a possibility: re-open in that case. |
I've looked at all of the related issues with VS15 (e.g. #2125) and the solutions are not working for me. I still have errors with resolving C functions such as _snprintf.
I've been trying to build this all day and have been unsuccessful. Any help would be greatly appreciated.
Steps taken:
Environment: Windows 10 x86, VS15 Community.
The text was updated successfully, but these errors were encountered: