On 2024-02-27 14:24, Gleb Popov wrote:
> On Tue, Feb 27, 2024 at 5:43 AM Alastair Hogge wrote:
>>
>> however, I do not know how that translates to Makefile
>> targets, like do-install-NON_USER_FACING_OPT-on. Currently the Makefile
>> target is of the ".if somecond FOO= .else BAR= .endif" form.
>
On Tue, Feb 27, 2024 at 5:43 AM Alastair Hogge wrote:
>
> however, I do not know how that translates to Makefile
> targets, like do-install-NON_USER_FACING_OPT-on. Currently the Makefile
> target is of the ".if somecond FOO= .else BAR= .endif" form.
I'm afraid you'd still have to write
post-inst
On 2024-02-23 15:05, Gleb Popov wrote:
Hi Gleb,
> On Fri, Feb 23, 2024 at 5:51 AM Alastair Hogge wrote:
>>
>> Hello,
>>
>> The current in-tree port of mame, 0.261, is built around the core
>> multi-emulation framework, which results in the usual mega monolithic
>> mame binary. There are options
On Fri, Feb 23, 2024 at 5:51 AM Alastair Hogge wrote:
>
> Hello,
>
> The current in-tree port of mame, 0.261, is built around the core
> multi-emulation framework, which results in the usual mega monolithic
> mame binary. There are options for TOOLS, which include two other
> emulators. The curren
Hello,
The current in-tree port of mame, 0.261, is built around the core
multi-emulation framework, which results in the usual mega monolithic
mame binary. There are options for TOOLS, which include two other
emulators. The current upstream release, 0.262 has enabled separation of
mame from the re
