how to install core and emulator with a script ?

wsamael

I gave 3do for example, in fact, i would install many core and many emulator with a script, but i don't know how to make it for that
This script is an example for explain what i wanna to do ;)

mitu

Then why don't you look at how other libretro cores are built and configured - in the RetroPie-Setup repository ?

wsamael

sorry for being late.

@mitu said in how to install core and emulator with a script ?:

Then why don't you look at

fbecause I'm stupid boy XD , ok my bad ;)

So I put it in /scriptsmodules/libretrocores/ (for libretro core ) but how can install it ? if i launch

sudo bash ./lr-bluemsx.sh

( for example ), that not install msx core in ES :(

mitu

@wsamael said in how to install core and emulator with a script ?:

So I put it in /scriptsmodules/libretrocores/ (for libretro core ) but how can install it ?

How do you install other emulators, already present in RetroPie ?

wsamael

actually I install it by ES menu ( retropie_setup.sh ) one by one but it's long and boring ;) so it's why I wanna instal it with a command in a script. like that I can install by group ( arcade, computer etc. I hope you understand what I would say ;)

mitu

If you wish to use the cli to call the script, then the syntax is

sudo ./retropie_packages <scriptmodule> <function>

where <function> can be one of the: sources, build, install, remove, configure, depends (may be more, but these are the main ones). These are defined in the scriptmodule as source_<module>, build_<module>, etc.
To install lr-fceumm, you'd call

sudo ./retropie_packages lr-fceumm depends
sudo ./retropie_packages lr-fceumm sources
sudo ./retropie_packages lr-fceumm build
sudo ./retropie_packages lr-fceumm install
sudo ./retropie_packages lr-fceumm configure

If you omit the <function> parameter, running sudo ./retropie_packages <module> will run depends, build, install and configure automatically.

wsamael

Yyyyyyeeeeeessssss it's work great, I've install two of them with a script for test and it's ok. Thanks U so much :)

wsamael

i' made all my script for install every core and emulators what i want, everything works great ( tahnks again :) ) but I wanna konw if it's possible to install them by binari, beacuse with this method

sudo ./retropie_packages XXX depends
sudo ./retropie_packages XXX sources
sudo ./retropie_packages XXX build
sudo ./retropie_packages XXX install
sudo ./retropie_packages XXX configure

it's ok but very long to add them by source.

mitu

Binary install means downloading it from the RetroPie server. If you added your own (new) scripts, there's nothing to download and install. Binary installation can be run via the install_bin parameter.

wsamael

@mitu

That's all ? ^^ Thank you :) I'll do that asap :)

wsamael

sorry it's me again ;)

i wanna complete all script and test it but i've a problem with path files for install packages

if I install via the ES menu

sudo ./RetroPie-Setup/retropie_setup.sh

the packages are install to /home/pi/Retropie/roms/ XXX
and If a Install via my script
for exemple:

sudo bash ./RetroPie-Setup/retropie_packages.sh cannonball install_bin

the packages are install in
/opt/retropie/ emulators,
/opt/retropielibretrocores
and /opt/retropie/ports

so i some package in /home pi ..../ roms, some in opt/retropîe/ XXX

any idea for install all packages in /home/pi/Retropie/roms with a script ? Because it's not easy to manage many roms folders in my es_system.cfg .

mitu

Packages (emulators/ports/etc.) are not installed in /home/pi/RetroPie/roms - which is used for ROMs and games. The default installation location is under /opt/retropie.

wsamael

Yes you're right ( but you know that XD ) but thé package install don't create roms folder in/home/pi... or of I install package buy es the roms folder has been create , how can i do for do the same install?

Where i launch my script nothing is create in /home../roms folder

mitu

@wsamael Sorry, I don't fully understand what it's not working. If you created your own install script and it doesn't work, then the script might be incomplete/incorrect.

Thorr69

I think he means that the roms directory isn't being created for the system he is installing. If you install experimental systems through the experimental packages, the rom directory for that system is created as well.

I think you are right the script is incomplete. He probably needs to add something at the end to create the rom directory.

wsamael

@mitu said in how to install core and emulator with a script ?:

@wsamael Sorry, I don't fully understand what it's not working. If you created your own install script and it doesn't work, then the script might be incomplete/incorrect.

I try to explain what i wanna

If i install a package via ES menu, that install the core and create a roms folder in home/pi/ RetroPie/roms/xxx

And the script install the core but don't create rom folder

And for port package that does'nt create port folder in home/pi...

mitu

Can you please be more specific ? Is this one of the packages included in RetroPie or something you created ? How do you - manually - run the package commands ?

wsamael

@Thorr69
Probably, but I don't know how to add command Line to create roms folder especially for port package like openbor

wsamael

@mitu said in how to install core and emulator with a script ?:

Can you please be more specific ? Is this one of the packages included in RetroPie or something you created ? How do you - manually - run the package commands ?

One of the package incluse in RetroPie,
I launch the install via Retropie_packages.sh mame2010 install_bin ( for example )

Mame has been installed but no rom folder in /home/pi ( Like the other package )

mitu

From one of the previous posts:

To install lr-fceumm, you'd call

sudo ./retropie_packages lr-fceumm depends
sudo ./retropie_packages lr-fceumm sources
sudo ./retropie_packages lr-fceumm build
sudo ./retropie_packages lr-fceumm install
sudo ./retropie_packages lr-fceumm configure

The rom folder is created as part of the last step - by the scriptmodule configure function. If you just run install_bin, that won't happen.