-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Build fails after commit 62765f1 #4285
Comments
Looking at the results for the merge build, there are errors reported, but that just appears to be a timeout while running the unit tests, which doesn't necessarily indicate a problem. And the build in the PR (#4213) was definitely successful. Maybe it is just me. |
My fork also fails to build with the same linker errors after the latest commit. |
You might be able to work around this by building GdiRenderer manually. I think I missed that in the dependencies for that project, but didn't catch it since GdiRenderer.lib was already built on my machine. I can take more of a look probably Wednesday at the earliest |
That didn't seem to help, but what did work for me was adding RendererGdi as a reference in the UnitTests_TerminalCore project. I don't know if that's the right solution, but it does at least build. For now, though, I'm just branching off the previous commit, so it's not a major problem. |
## Summary of the Pull Request In #4213 I added a dependency to the `UnitTests_TerminalCore` project on basically all of conhost. This _worked on my machine_, but it's consistently not working on other machines. This should fix those issues. ## References ## PR Checklist * [x] Closes #4285 * [x] I work here * [n/a] Tests added/passed * [n/a] Requires documentation to be updated ## Validation Steps Performed Made a fresh clone and built it.
Environment
Steps to reproduce
Expected behavior
The build should succeed.
Actual behavior
I get the following errors:
If I checkout one revision back (77dd51a), the build succeeds.
Is this just me, or is something busted?
The text was updated successfully, but these errors were encountered: