BIOS paths in Portable Mode

[scottluker]

When using mGBA in portable mode, if the BIOS paths are in the same directory as mGBA then they should be a relative path rather than an absolute path. This will make mGBA fully portable because you won't have to manually change the paths.

Or another solution to this is to have mGBA check a folder which you can place the bios files in and will be automatically used.

[scottluker]

I know I can use .\ on windows, just though this would help other people.

[endrift]

It should automatically look in the same directory as the config file. If that's not working in portable mode that's a bug.

[twoco]

If you use ./ or no prefix (e.g. only bios/foo.bin it tries to locate the file from the ROM directory. It's ok. But how to define the relative path from the application folder where the mGBA.exe is located? Maybe both solutions are useful. Relative path of ROM and relative path of application. Use case: Either load and save files in ROM directory (with optional subfolders) as it currently works. Or organize all in the application path (portable). This is currently only possible with absolute pathes. Or did I miss something?

v0.10.2

[endrift]

that sounds like a bug

[twoco]

Not sure if this is a bug. Because you maybe want relative path to ROM directory. But also realtive path to the app (exe) folder is also a good option. But how to handle both. Or what is intended/expected?

We could use variables like {app}/bios/foo.bin and if nothing is set like ./bios/foo.bin uses from ROM dir.

[endrift]

Expected/intended is relative to the app folder.

[twoco]

Ok, I started the ROM by double click one the file and open with (from Windows explorer). Not yet tried when open mGBA and open file manually.

[endrift]

Oh, I think that might be a different bug. I'd need to find the bug report for it though.

[endrift]

I believe it's #2826, which is fixed in dev but not in 0.10.2. Can you see what it does in a dev build?