@sleve_mcdichael said in Is there a guide somewhere to create install scripts if you can get a game to compile?:

What is the significance of the CMakeLists.txt param in ...

The correct way to invoke cmake is

cmake <PARAMS> <path_to_folder_containing_CMakeLists.txt>`

... the && cd build part didn't do anything, so it tried to cmake & make from the wrong dir and, predictably, failed.

Don't use && then, just have the 2 commands separately.

.. this one just built it right there in the main tmp/build/module folder. Do I want to leave it in or out? Does it make a difference?

No, but some programs enforce a separate build folder (out-of-tree build) so you may get an error when building directly in the source folder.

Also, it still made the same file, but it put it in the wrong place. So if I were to use retropie_packages.sh <module> install after this, it would be installing the old one from the "build" dir and not the new one I just built in the wrong place, so this isn't a solution.

If you change the build parameters, then do a cleanup first.

I think I could begin the build function with a [[ -d build ]] && rm -rf build to remove the dir if it exists?

I don't think that when building with cmake this step is necessary, so that's why is not enforced. This is an issue only when repeatedly re-building without cleaning up, so it's more of an artifact of re-trying the build with a 'dirty' state.
You should first compile the program separately - not as a scriptmodule - to get the cmake build options right, then add it to the build function and try it from retropie_packages.sh.

reason the png looks like that is because i made to fit into my updated theme.

ok i understand thank you ;)

I did get my .mp3 files to play inside the music folder. I am happy that .mp4s work as well. I could have sworn that one of the read me files said that you could also place these inside a video folder so that they will play randomly like the .mp3s. If this isn't the case, hopefully that option will be included in a future build. I have to say that these new options (grid view, video view, basic view) have been implemented nicely. The presentation of the themes looks more vibrant too :-).

Press Start to open the Emulationstation menu, then use the Input Configuration entry to re-configure your controller.

@kok00 don't know anything about the script but for the record there are some non working parents that are required to make clones work so if you delete them they may break more games depending on the type of rom set you have.

MODERATION NOTE: I merged the 2 topics you opened. If you find your posts flagged as spam, try removing the code blocks first when posting.

@mitu said in How does one make a script module for an emulator / branch:

@HoJo215 said in How does one make a script module for an emulator / branch:

DRI3 was the problem.

Isn't this a runtime settings for your X.org configuration ?

Actually I think it's part of the graphics or at least shader profile being used in mesa.
I have padoka's bleeding edge repository in use.. Otherwise known as unstable.
So things can go awry.. Like they did until I took a gander at the Makefile, saw some unused options, put 1 + 1 together and made some edits.. It worked a out beautifully.
Especially on the Flycast-Wince emu with the same Makefile edits. I'm playing Sega Rally 2 on 2x internal resolution, 2x br and a 4x pass xbr shaders without one hiccup.

Keep in mind this my first run with retropie x86. I decided to make small form factor emu box a month or so ago and gripped up a coffee lake NUC to guinea pig with. So everything is trial & error as I run with it.

@bleckman Look at how the Ports scripts are created - for instance Kodi - and you can replicate it to start the media player. Install Kodi, look at the kodi.sh script that it creates in the ports folder, and copy it and replace the Kodi start sequence with the command to start the program - from the author's instructions.

This discussion shows why options are preferable to suit the many different tastes, but they do require more effort in development. Thus the invitation to help creating the features requested.

As a long-time Linux user who uses GUIs as naturally as the command line, I understand both sides. A pretty design doesn't contradict functionality per se, but in reality it tends to reduce the available options, since they have to fit into the design. And prettiness lies in the eye of the beholder anyhow.

I often compare software design to cars: everyday controls are best placed on the dashboard, the rest goes under the hood. There will always be exceptions that depend on personal preferences rather than functionality, but even among car enthusiasts only a select few care about the visual design of the engine compartment. :) But I think we shouldn't shun the ones who do.

@dudleydes yes I tried that as well.

UPDATE: everything is working perfect now. the trick was updating the binaries. :) Geez I should have started with that a week ago haha.

-thread closed-

I figured out the issue. Problem was I got an error when I followed MSL's instructions to the letter. First time I got an error saying something like "this can not be a service", second time it said "Failed to execute operation: Bad Message". I mistyped. The script:

[Unit]
Description=RemotePi Board Shutdown Service
Before=multi-user.target
Conflicts=shutdown.target
[Service]
ExecStart=/bin/true
ExecStop=/etc/shutdown.sh
Type=oneshot
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target

I had "Service" on a line by itself. Doh! It's fixed now, powering on off works perfectly now. Hooray!

@SuperMagicom said in switch between Emulation Station & Attract Mode:

There are scripts for this in the Motion Blue base image.

thanks for the help,

are these scripts available without having to download the Motion Blue image?
if so where can i get them?

Nevermind.