I'm building a custom MAME for my own use with fewer games than the normal build. However I'm not using the tiny build, since I'm keeping hundreds of games anyway, so I was only deleting the games I don't want from mamedriv.c
I know this way I will still compile lots of things I don't want, but that's not a problem for me.
The strange thing is that while doing this I discovered that I cannot leave only the driver "galaga" without also having the "qwak" driver, since the compilation will fail while linking:
Compiling src/mame/mamedriv.c... Compiling src/version.c... Linking mame64... obj/sdl/mame64/mame/namco.a(galaga.o):(.rodata+0x72f8): undefined reference to `device_get_config_atari_vg_earom(device_config const*, unsigned int, deviceinfo*)' obj/sdl/mame64/mame/namco.a(galaga.o):(.rodata+0xb5b8): undefined reference to `atari_vg_earom_r(running_device*, unsigned int)' obj/sdl/mame64/mame/namco.a(galaga.o):(.rodata+0xb5c8): undefined reference to `atari_vg_earom_w(running_device*, unsigned int, unsigned char)' obj/sdl/mame64/mame/namco.a(galaga.o):(.rodata+0xb5f8): undefined reference to `atari_vg_earom_ctrl_w(running_device*, unsigned int, unsigned char)' collect2: ld returned 1 exit status make: *** [mame64] Error 1
Once I also add the "qwak" driver it compiles fine. I think there are other cases of dependencies like these.
Can someone explain why does this happen and what would be the workaround? Is this expected behavior?
(A clean compile didn't solve the problem)
|