-
Notifications
You must be signed in to change notification settings - Fork 7
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
Use a self-hosted runner for the Windows build. #124
Conversation
@lilleyse and I think that we need the image to have the Also, you may want to add |
Ok cool I'll add those. If you want, you can add those Choco commands to the beginning of your build script as a test, to make sure nothing else is missing. And then remove them once the image is updated. |
Well, the image is updated, but it's still not working. If you look at the beginning of the Configure step, where it lists all the environment variables, you can see that |
cl.exe didn't help. The problem seems to be that the PATH and other environment variable updates done by |
Installing Powershell 7 fixed that problem. On to the next... Conan seems to be having a problem with long paths. See here: I confirmed that the image has long paths enabled:
And I also tested it by creating the file that Conan is complaining about, and it was successful. So there's probably a problem with Conan itself or something it uses that prevents the use of long paths (which is, infuriatingly, a really common problem). This is showing up because the workspace directory used by Github-hosted runners is much shorter than the one in this self-hosted runner. I couldn't work out how to fix that in the short term I was willing to spend on it, but have added a partial workaround for now by using "d:" as the Conan directory. The actual workspace directory is just a symlink to d:\ anyway in this runner image. That makes Conan happy, but cmake is still losing its mind. I guess I'll need to fix the workspace directory for real. Perhaps I've somehow failed to actually enable long paths? But I don't see how. |
Ok this should be in good shape now, after moving the action runner working directory to |
236747e
to
53353eb
Compare
I thought we were safe from long path issues... oh well... the workaround is fine for now. Thanks @kring for setting this up for us. |
No description provided.