libretro-db Makefile fails (MINGGW64 Windows 11)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Following instructions from
https://github.com/libretro/RetroArch/blob/master/libretro-db/README.md
git clone https://github.com/libretro/libretro-super.git
cd libretro-super
./libretro-fetch.sh retroarch
cd retroarch
./configure
cd libretro-db
c_converter "NAME_OF_RDB_FILE.rdb" "NAME_OF_SOURCE_DAT.dat"
gives
bash: c_converter: command not found
So I try to run the Makefile and get the following
cc -I. -I../libretro-common/include rmsgpack.c -c -g -O2 -Wall -DNDEBUG -o rmsgpack.o
Makefile:55: recipe for target 'rmsgpack.o' failed
process_begin: CreateProcess(NULL, cc -I. -I../libretro-common/include rmsgpack.c -c -g -O2 -Wall -DNDEBUG -o rmsgpack.o, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [rmsgpack.o] Error 2
I also tried the ./libretro-build-database.sh script from /libretro-super and get the same error
tried make on the retroarch folder incase something wasn't complied and get this message
CC input/input_keymaps.c
input/input_keymaps.c:70:20: fatal error: dinput.h: No such file or directory
#include <dinput.h>
Any idea what I am missing please?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with libretro-db/README.md and the libretro-db Makefile, then reproduce the c_converter build command under the reported MinGW64 setup. Check the reported compiler and dinput.h failures across libretro-db and input/input_keymaps.c; done means identifying the missing build prerequisite or documenting a reproducible Windows build fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 24/100