-
Notifications
You must be signed in to change notification settings - Fork 16
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
can't build #1
Comments
ninja and meson installed STDERR: |
I managed atleast to point the build system to build cassiaext (I see here to build cassiapp, you need to build cassiaext first) using the |
i think we can avoid this cassia-ext by understanding what .kt scripts need |
hi. i have managed to build cassia-ext using your fork, and had some troubles with gamescope compile errors, but after some trials and error, and a bit of workaround, i was able to build cassia-ext and it have generated an .gz archive, now, how do i use it/integrate into the app? |
Okay, could you please upload the gz file here or somewhere so I can investigate a bit too? It would be also nice to say how you got it compiled too. |
i have tried importing libdrm into cmake, manually changng the gamescope files, to be able to locate drm headers, and i have removed a lot of code from gamescope hdmi.h, to fix some compile errors. i also didn't have any error related to libtool. i will redo all steps, to ensure everything is fine, and send you as patch or PR, whathever you want. also, i will send the compiled cassiaext file from google drive. cassiaext prefix: https://drive.google.com/file/d/14EIlGqyw2_p60vKIG-uZuC3054GJM8TG/view?usp=sharing |
Yep. |
i'm also. do you have dc or telegram? |
I do have DC |
so, can we continue on dc? |
Okay could you send me request? Mine's also the same as github. |
FATAL EXCEPTION: main |
Me and @rlukas210 have managed to make cassiaext and cassia-runtime sucessfully compile. You can see in my forks that I have automated the compilation with a |
where shuld i get and put prefix and runtime |
how to setup build?
The text was updated successfully, but these errors were encountered: