-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature: Windows support for wcc (MinGW64) #156
Comments
Would you send a pull request, or tell me how to solve the problem? |
Yes I understand, I guess it would be better to split up in multiple PRs to keep overview. I've contained nearly all of the conditional code to a separate util file called |
This should be the complete patchset for wcc. |
After careful consideration, I would like to reject this pull request because it is difficult for me to support the MinGW64 platform. |
I understand as the changes are quite substantial. I will focus my own fork on Win32 compatibility instead: https://github.com/ijsf/xcc-win32 |
I was wondering if there would be interest to make
wcc
natively compatible with Windows (64-bit) by using the MinGW64 toolchain using MSYS.I've managed to successfully port
wcc
to MinGW64 and make it useable under Windows, as I have a need for a lightning fast C to WASM compiler andwcc
seems to fit the bill 🏆It seems that scope of the changes are more or less:
long
(not 64-bit on Windows) tolong long
to explicitly use 64-bit and still allow for arithmetic.fmemopen
,tmpfile
as well as process handling such asfork
.C:\\A\\B\\C
as well as POSIX paths transparently.wchar
.My changes are passing all
test-wcc
tests. I've tried to keep the changes as unintrusive as possible to avoid regression, but there are still a large number of changes.For other targets like
xcc
, it seems much less logical and I have not touched any of these, namely, the compiler will produce ELF output which won't be able to run natively on Windows, unless something is added to accommodate this.The text was updated successfully, but these errors were encountered: