-
Notifications
You must be signed in to change notification settings - Fork 2
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
GitHub CI issues for Base64::Native on Windows #2
Comments
- replace Travis with github workflow, including Windows. - not sure what's with appveyor. try to fix proejct link, as least
I just kicked off a build. Appveyor project now seems to be here Also made first attempt at a github testing build failing with missing nmake in LibraryMake dependency |
Hmmm, so passed in AppVeyor for you at least, that's good. Perhaps something that Chocolatey provides that needs to be manually installed in a GitHub workflow? Ah yes, I can see |
Appveyor working at least, but still trying to figure out github windows testing. choco installs work on latest attempt , but still not picking up nmake. |
(For reference, 8a0e5ef is because of this issue.) |
hopefully fixed in db39b0d. I changed the Build.pm6 to rety using gcc and make, if the initial Visual Tools flavored build fails on Windows. |
further refined after reading croservices/cro#105. Looks for |
Hmm, LibraryMake dependency is still failing its tests and currently needs a forced install. |
I'm thinking of trying another approach.. Maybe the win dll could be built as a github build action and distributed rather than being built at installation. |
Have set-up a github workflow to build the DLL. Getting a github test failure on HTTP::Status, as aby-product of switching to Native::Compile which has this as a depdendency. |
Now working reasonably well on master, except for need to force install LibraryMake. I've raised a PR for this. Runs a |
I am building another module on top of
Base64::Native
, and can't get the GitHub Workflow CI to work on Windows because of this error from the zef build phase during dependency installation:Your badges indicate that it's passing on AppVeyor, but when I click on the Windows badge, AppVeyor tells me
Project not found or access denied.
so I can't see when it passed or with which version of Rakudo, to compare against what GitHub Workflows is using.Would you mind taking a look and checking whether it still passes for you?
For what it's worth, this is the Rakudo version that GHWF is apparently using:
The text was updated successfully, but these errors were encountered: