- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 7
          test x86_64-pc-windows-gnullvm to see if it works
          #120
        
          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
base: main
Are you sure you want to change the base?
Conversation
| Codecov ReportAll modified and coverable lines are covered by tests ✅ 
 Flags with carried forward coverage won't be shown. Click here to find out more. see 2 files with indirect coverage changes 🚀 New features to boost your workflow:
 | 
26e99f2    to
    ac59fc5      
    Compare
  
    | @bjorn3 do you have recommendations for installing a linker that works here? | 
| https://www.mingw-w64.org/downloads/#llvm-mingw points to https://github.com/mstorsjo/llvm-mingw/releases for getting an LLVM based MinGW toolchain. I think https://github.com/mstorsjo/llvm-mingw/releases/download/20250709/llvm-mingw-20250709-ucrt-x86_64.zip would work. You need to configure the  | 
1777425    to
    35e025e      
    Compare
  
    | hmm, so no it does not work?  | 
| You may need to add the right lib directory to the  | 
95f9f5c    to
    ab898fa      
    Compare
  
            
          
                .github/workflows/checks.yaml
              
                Outdated
          
        
      | run: | | ||
| echo "llvm-mingw/llvm-mingw-20250709-ucrt-x86_64/bin" >> "$GITHUB_PATH" | ||
| echo "llvm-mingw/llvm-mingw-20250709-ucrt-x86_64/lib" >> "$GITHUB_PATH" | ||
| echo "llvm-mingw/llvm-mingw-20250709-ucrt-x86_64/armv7-w64-mingw32/bin" >> "$GITHUB_PATH" | 
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.
This should be the x86_64 path, not the armv7 library path, right
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.
eh yes. but also I don't think writing to the github_path would actually have much effect here.
clearly, I have no idea what I'm doing here, and it's tough to debug in CI
43d6f99    to
    b601425      
    Compare
  
    | well, idk, feel free to give this a go but it's very user-hostile. Does anyone use this stuff? | 
cc #119