Open peblpebl opened 5 years ago
@peblpebl thanks for submitting. @pejovica does that fix look right?
@peblpebl I'm not completely sure what are you trying to do, but cygwin-amd64
should be a binary for Cygwin, and not for Windows. So, if you need a Cygwin ninja you could mark NINJA library as optional on Cygwin (like it is done for Solaris), in which case the binary from your environment will be picked up.
On the other hand, if you are trying to build for Windows (and only use Cygwin as a shell), you might be better off using the native Windows Python instead of the Cygwin one. It may happen that things will work better in that case.
I am trying to build a native image of a java project. Given win in not supported yet, I have a virtualbox with ubuntu that shares a drive between guest/host. When I see that is working, I want to try to see how far I get with a native image of windows. Secondly I want to see how fast I can get a R script to run (it uses some fortran libs). But I am currently stuck at mx eclipseinit.
@peblpebl we are now considering to remove cygwin environment support altogether: https://github.com/graalvm/mx/issues/189 Can you please confirm that mx works for you when run with a standard Windows python executable.
I am trying to run in mx in cygwin, but am getting:
when just doing mx update.
Adding
to mx.mx/suite.py, seems to help, but I dont know if this is the right way.