Lime-3DS-Emulator
Lime-3DS-Emulator copied to clipboard
ryzendew
android: Implement option for emulation-orientation
See #267
This adds a setting in the theme-section to override and specify the desired orientation for the emulation.
@OpenSauce04 Is it possible to extract the lime-library from the latest release and use it in debug-builds instead of building them myself? Currently i don't actually have a working emulator, just its frontend. It is enough for this PR, but in the future i might look into working on some other android-things, and it would be nice to have a fully working emulator, and i am not to keen to install all the required dep's in my already bloated system.
Are you saying that you can't build the program yourself or that you can't test it? It's hard to tell.
I can build the android apk, but not lime-emulator itself.
So the resulting android apk is missing the liblime.so (i think thats what it is called) that actually contains the emulator.
That means my app can do everything, except running a game.
(I basically opened src/android/ with android studio and started building the app)
If i have to figure out how to build the entire stack, i will, but it would be nice to have a shortcut so that i can only focus on the frontend, in this case android.
I'm not sure how you managed to do that, I've set up a development environment on multiple machines using both Linux and Windows and it's just as simple as installing Android Studio and running the project. You don't usually need to do anything else.
I've set up a development environment on multiple machines using both Linux and Windows and it's just as simple as installing Android Studio and running the project.
You mean the full dev-setup as described in the wiki? Yeah, i skipped that because i dont have the dependencies installed. I just opened the android-subfolder in android studio and build only that. That (obviously) leads to the lime-binaries missing in the android artifact. I'd like to use existing files as a drop in-replacement. At least for android, that simplifies the setup quite a bit
You mean the full dev-setup as described in the wiki? Yeah, i skipped that because i dont have the dependencies installed.
This is the entirety of the Android section of the build documentation:
There are no other dependencies if you are building for Android. I would know because I use local Docker containers when building for Linux, and don't have the build dependencies installed directly to my system.
There are no other dependencies if you are building for Android. I would know because I use local Docker containers when building for Linux, and don't have the build dependencies installed directly to my system.
I did have to install llvm-15-linker-tools on ubuntu, but after that it was building fine.
Also, the emulator was the issue, i overlooked that it should have been an actual device.
The issue i currently have is that moving the setting to an IntSetting() creates some kind of race condition. Only on exit the setting saves, but it takes a while. Before that has happened, the emulator calls the onReturn and re-initializes the orientation, but with the outdated value. And i guess then the saved value gets lost after quitting the game.
Should i not use an IntSetting in favor of the current "full implementation" like the other settings in the theme one?
@newhinton You can also use Github Actions to build test programs on your fork. Click on the Actions tab, it'll give you the option to turn it on. Then whenever you push a change on a branch, it'll start building and you can download the various artifacts to test them out.
Please mark the previous discussions as resolved once you have addressed the relevant feedback
You can probably wait with that, there is a bug in how the core deals with rotation: https://github.com/PabloMK7/citra/issues/193
FYI you shouldn't be using master for PRs because it causes complications when you need to make a new branch. Always use feature branches for each PR.
