Some questions about retropie script modules

[meleu]

I'm trying to write a custom script module to automate some steps to achieve what @RetroResolution instructs to enable RetroArch to record a gameplay. And then some doubts arose.

1. Is there a way to show a script module in retropie_setup menu for a specific architecture only? In my specific case I want to show only when executing retropie_setup on raspi2 or 3.

2. [Just a matter of curiosity] In the retroarch.sh for RetroArch installation there's a function build_retroarch that executes commands that are supposed to be called when the current working directory is a very specific one (./configure, make, etc.), but there's no cd command in the function. Obviously the script changes the working directory at some point, but where?
   I'm asking it because my custom scriptmodule needs to cd a couple of times to compile some codecs. It's pretty simple to record the current working dir in a variable before all the cd's and get back to that after the codecs compilations, but is it really necessary?

[vbs]

@meleu said in Some questions about retropie script modules:

1. Is there a way to show a script module in retropie_setup menu for a specific architecture only? In my specific case I want to show only when executing retropie_setup on raspi2 or 3.

Yes you can do that. Take a look at uae4arm.sh, it does it also.

rp_module_flags="!x86 !mali"

That module is not available for x86 and mali and will not show up in "Manage Packages".

[meleu]

@vbs Hmm... I have to explicitly put what architecture I want to NOT show. Then the next question: is there a flag list somewhere?

[vbs]

@meleu
I think the best you can get as a list is the getPlatform function that determines the current platform:
https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/system.sh#L150

And this is where the package filtering based on the platform takes place:
https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/packages.sh#L362

As far as I can see it is working as a blacklist only, but not so sure, my "bashish" is too bad. :)

[BuZz]

as @vbs said - you can only "exclude" platforms etc.

platform flags are

arm armv6 armv7 armv8 neon mali x86 x11 rpi rpi1 rpi2 rpi3

[BuZz]

I missed out armv6.

[cyperghost]

I want to create a scriptmodule for OpenBOR to add version 6315. I see the flag rp_module_id="openbor" that makes the module visiable into script screen. To avoid confusion I want annother name like rp_module_id="openbor_6xxx but want to use the old pathes.

Now all instances of $md_id, $md_config... uses the name that is given by rp_module_id so how to change names? I can include a function strip () { }that sets internal variables to openbor but this is not good code. So how to achive this?

Again: the goal is to use one config directory and one directory that contains several versions of OpenBOR.

Besides thank you BuZz for the platforms flags, I may exclude 6xxx for rpi1.
Is there a dedicated WIKI about script modules?