| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 システムコア | 低 | 認証済み | 未処理 | 2019-03-06 01:04 | 2019-03-07 20:00 |
| テスター | Tafoid | 担当者 | ソース | ||
| バージョン | 0.207 | 発生バージョン | 修正バージョン | ||
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | LISTXML | ||||
| セット詳細 | |||||
| 概 要 | -listxmlでデバイスのsourcefileがフルパスで出力されることがある。 | ||||
| 詳 細 | For the same devices each time, the "sourcefile=" source path contains fullpath information rather than relative paths starting at "src". I noticed this starting to happen when I began to compile daily builds on a RAMDISK (R:) - specifically r:\mame contains the source, with the devices in question showing "r:/mame/src/......" as "sourcefile=" rather than "src/......" | ||||
| 再現手順 | |||||
| 追加情報 | I noticed looking at the source which controls this @ "src\frontend\mame\info.cpp" that effort is made to parse this literal path information from the normal non-device machine sourcefiles - but no effort is made when the device machine line is created. The problems that show up for me involve only 2 locations (making up 58 devices as of this writing): - <machine name="dac" sourcefile="r:/mame/src/devices/sound/dac.h" isdevice="yes" runnable="no"> - <machine name="i80c51" sourcefile="r:/mame/src/devices/cpu/mcs51/mcs51.cpp" isdevice="yes" runnable="no"> The remaining devices (4278 as of this writing) are showing the relative path as expected. | ||||
| 添付ファイル | |||||