-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
MIPS64 Support #526
Comments
I have triggered success travis builds (They all failed at upload to s3) for all the libraries possible listed below. Links of my travis repo are either here. I'm dummy to the Java and ANT stuff, please teach me what should I do next, thanks a lot. |
Hey @FlyGoat, I have reviewed everything above, great work. Please go ahead and open a PR in all LWJGL-CI repositories. The changes will be merged manually (need to have a single commit on top of upstream, for simpler maintenance), but the PRs will serve as credit to the effort you made. After the binaries are available for download, you can then test the lwjgl3 changes and we can discuss what else needs to be done there.
That's OK. LWJGL has been stuck to GCC 4.8 and I would really like to move to a newer version. I will open a separate issue to discuss the implications another time.
That's because the AWS credentials can only be decrypted when building from the LWJGL-CI repositories.
I'm afraid this might be a showstopper in a future LWJGL version. The plan is to use tinycc as a poor man's JIT compiler for JNI bindings. |
Thanks for your kindly instructions. There are some rebase works for me todo and I will send pull requests tomorrow. For the tinycc issue, is it possible to integrate a strip down version of clang instead of tinycc for architectures it doesn't support? Although it might be larger. |
Size is indeed the main issue for LWJGL. It needs to be small enough to be embedded to the core lwjgl shared library and support all relevant architectures/ABIs. Feature-wise we don't need much, it will be used for simple downcalls/upcalls only. I'm still looking for alternatives and I'm open to suggestions. |
Btw: It seems like MacOSX doesn't supported by tinycc too? On these unpopular platforms, probably we can fallback to system CC. Just give them a chance to play "portable games". |
I have set up PRs for all Ci jobs. |
I have managed to upload CI builds to my own S3 bucket and build lwjgl3 itself on MIPS64 platform.
Now I have managed to run Minecraft on my MIPS64 laptop, it just works~ |
Hey @FlyGoat, Is it OK if I bump all scripts from |
I think it should be fine. |
Hey @FlyGoat, All LWJGL-CI projects have migrated from Travis-CI/AppVeyor to Github Actions and two new architectures have been added (macOS ARM64 & Windows ARM64). The MIPS64 builds are also in there, but I had to comment-out a lot of them. I kept hitting various issues and didn't have time to fix them. Would you be so kind to investigate and submit fixes? Thanks! |
I'm interested in make LWJGL3 work on MIPS64 platform, just for Minecraft :-)
But I have no clues on how to bootstrap LWJGL on a new platform, I'm too stupid to make a successful offline build.
Referencing #495, I did some modifications to let build system identify MIPS64 architecture, also tried to trigger Travis CI build for libraries used by LWJGL.
There are serval problems:
And I just made a list of binaries that I should be working on:
Am I doing that in the right way? Did I miss anything? Please give me some hints, thanks in advance.
The text was updated successfully, but these errors were encountered: