-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Quarkus Native Image build on Windows fails #8256
Comments
Hi, Can you please give version |
I am sorry, i wrote down the wrong version. I am actually already using 1.3.1.Final. Running like this:
Result:
|
So, the execption looks to be the same as here: #6884 |
This issue can be closed. I think i did a mistake. See explaination here: https://groups.google.com/forum/#!topic/quarkus-dev/kC3vhDyuNuQ |
Describe the bug
I am currently trying to evaluate if Github Actions can be used to build Quarkus Native Images for all major operating system. Linux and MacOS work find. Only the Windows build fails with.
Build Result
If you look at the repo you will see: It is Quarkus 1.3.1; and the build is based on Gradle which should not make a different. Due to the problem describe here, i am not invoking the gradle-task to build the image, but native-image directly.
I am seeing the same issue on graal 19.3.1-java11 and graal 20.0.0-java11. The issue is only on Windows. With 19.3.1 on Linux and MacOs there is no problem.
With the java8 equivalent i am not even getting this far. Native Image failed without much output but only an obscure error-code Build with graalvm-19.3.1-java8
To the best of my knowledge the windows runner used by Github Actions has all that is needed installed (What's needed?): Visual Studio 2017 Enterprise Edition.
To Reproduce
Steps to reproduce the behavior:
Environment (please complete the following information):
mvnw --version
orgradlew --version
): gradleMaybe someone has an idea/tip. I think it would be quiet nice if Github Actions could be used to build native binaries for all major platforms...
The text was updated successfully, but these errors were encountered: