Compiling MAME, how to specifically use the SUBTARGET and SOURCEFILTER parameters.

[wolffy1998]

Does SUBTARGET default to searching for .lua, .lst, and .flt files in /script/target/mame/ and /src/mame/? What is the difference between .lst and .flt, and how should .flt be defined?

I used make subtarget=whatever sourcefilter=myflt.flt, and then wrote the following in myflt.flt: +nes +snes, but no games were compiled.

[holub]

https://docs.mamedev.org/initialsetup/compilingmame.html#all-platforms

[wolffy1998]

In .flt, writing it this way works fine.

but writing it this way cannot be recognized.

[cuavas]

Does it work if you add at least one source file directive? If you look at src/mame/nl.flt it does use + directives to include individual systems, but it also has several source file directives.

[wolffy1998]

I have already reviewed the document, but I still don't quite understand some of the details, such as the questions above. Then I wanted to ask whether the principle of subtarget is to first find the .lua script and then look for the .lst or .flt files in /src/mame for filtering.

[holub]

In general SUBTARGET provides couple presets (e.g. tiny buld). If you just set custom subtarget, the only effect you'll get - renamed executable.
What you are trying to achieve is done with help of SOURCES param.
You can use subtarget in this case or manually rename executable after.

[cuavas]

If you provide the SOURCES=... or SOURCEFILTER=... it will use that directly.

If you set SUBTARGET but don’t set don’t set SOURCES or SOURCEFILTER, it will look for corresponding Lua and lst files (e.g. see how SUBTARGET=tiny uses scripts/target/mame/tiny.lua and src/mame/tiny.lst). If that fails, it will look for a corresponding flt file (e.g. see how SUBTARGET=virtual uses src/mame/virtual.flt – there are no corresponding Lua and lst files).

[wolffy1998]

Okay, I understand your reply.