Open alexdean08 opened 1 year ago
Hi, thank you for reaching out.
Supporting Android should not require changing or removing the X11 and Wayland code paths, but instead requires adding new code paths specifically for Android windowing subsystem as well as other OS specific paths, for example, for attaching GITS to apps.
We'll scope out the work to add Android support. If you'd like to add the support yourself, we'll be happy to help and review a PR.
Thank you!
I actually have another question relating to this. I noticed that there are flags WITH_OPENCL and WITH_VULKAN, however no flag WITH_OPENGL. Is there a reason for this? I am primarily looking to use GITS for OpenCL and if I "remove" OpenGL in the build process using a flag WITH_OPENGL=OFF, then I should be able to use GITS for Android because OpenCL doesn't need X11 and Wayland.
Hi, We don't have a flag WITH_OPENGL, because in the past we haven't had a need to disable OGL on any platform.
We'll scope out the work to add this flag. Of course if you'd like to add the flag yourself, we'll be happy to help and review a PR.
I really like the GITS project. I've gotten it built on Windows and have been using it without issue on my personal projects.
I was wondering about Android support? GITS seems to be heavily dependent on X11 and wayland for Linux machines, but those libraries aren't supported by Android. Is there a known way to go around this? Even only for OpenCL which shouldn't require the libraries? With how extensively used X11 and wayland are in the codebase, it doesn't seem wise to remove them for Android and OpenCL support.