search

mamedev / mame

MAME
https://www.mamedev.org/
Other
7.77k stars 1.96k forks source link

Device source locations output in XML are not correctly parsed #9302

Open Tafoid opened 2 years ago

Tafoid commented 2 years ago

I am not sure if this is some wacky side effect of using a RAMDISK to hold my compile environment or even something in the new toolchain, but I just recently noticed and have traced the primary issue back to when I changed the tools to the most recent package available HERE.

In short, when I attempt to obtain an output of -listxml for data extraction, each device entry in the XML shows a full path for the source location.

Example

BEFORE: <machine name="tilemap" sourcefile="src/emu/tilemap.cpp" isdevice="yes" runnable="no"> AFTER: <machine name="tilemap" sourcefile="r:/mame/src/emu/tilemap.cpp" isdevice="yes" runnable="no">

I have a RAMDISK created in logical drive location R:, sized 32GB, as a FAT32 formatted HDD. Sadly, due to problems with the current package's LLD (faster linking) and use on RAMDISK due to some obscure flags, I'm stuck using the default LD and its hour+ long link times for a full MAME project.

Any ideas or clue on where to look or how to fix this issue would be appreciated.

cuavas commented 1 year ago

Does this still happen? Standard builds show paths relative to the src directory.