-
-
Notifications
You must be signed in to change notification settings - Fork 762
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
Xmake's mingw experience needs to be improved on windows #3960
Comments
try pass os.vrunv("./configure", argv, {shell = true}) see
|
That didn't work. I still got the same error. I'm using msys ucrt64 environment |
what's your subhost? let me see your output of or you can debug here Line 776 in bdb28e5
|
Subhost is windows. Host is also windows. Both in the msys shell and windows shell with mingw in the path. I'm on xmake 2.7.8 in mingw and 2.7.9 on windows. |
I have merged it. thanks. |
Is your feature request related to a problem? Please describe.
Sometimes it's useful to use xmake with mingw on windows e.g. because of compiler static analysis, but it seems like some of xmake's assumptions don't play well with MinGW on windows. As an example, the extraction logic assumes that Windows can't have a working tar program which is not true if the user has a MinGW environment. Another example is the
package.tools.autoconf
doesn't seem to work. It fails with the error:Describe the solution you'd like
Since mingw works on all OSes, maybe the way to go here is to not assume that unix tools are unavailable in windows hosts.
Describe alternatives you've considered
I've worked around the extraction issue by using a windows shell with MinGW in the path environment and it extracts the tgz archive correctly. I've also worked around the autoconf tools issue by calling the scripts through env:
Additional context
No response
The text was updated successfully, but these errors were encountered: