Consider naming wrapper script Makefile.rom the same as the original SGDK makefile makefile.gen -- v0.7.1: No rule to make target '/src/boot/sega.s'

[Tim5000]

Might be something I'm doing wrong as I'm only a dabbler with this but it is fun!

Building projects now fails early on with

/bin/mkdir -p src/boot
/bin/mkdir -p out
make: *** No rule to make target '/src/boot/sega.s', needed by 'src/boot/sega.s'. Stop.

As I installed the dpkg over a previous version, if I change the symlink sgdk to point to the earlier sgdkv1.51 the builds complete OK. Switching back to sgdkv1.62 makes the error happen again.

Running on

• Ubuntu 20.04
• VS Code 1.57.1
• Genesis Code 1.3.2

[kubilus1]

I just tested the samples directory and I was able to build those with the debian package of gendev 0.7.1. Can you verify what makefile you are using?

Try: make -f /opt/gendev/sgdk/mkfiles/Makefile.rom as that wraps the default SGDK makefile in critical ways.

[Tim5000]

Thanks, that appears to be promising!

Looks like the Genesis Code 1.3.2 plugin uses make -f $GENDEV/sgdk/mkfiles/makefile.gen as the default makefile - I've now configured it to use a custom makefile of $GENDEV/sgdk/mkfiles/Makefile.rom, wiped the boot files from the project so they can be recreated and it does now build and run up in my emulator.

The program doesn't appear to working properly now but I strongly suspect that there will be things I need to update in the program to cater for sgdk 1.62 which I haven't yet taken care of.
EDIT: yes the program called for me to change VDP_waitVSync(); to SYS_doVBlankProcess(); and now does appear to build and run correctly.

[kubilus1]

Excellent! I am not familiar with Genesis Code, but it looks like it's a plugin for Visual Studio. I suppose I could consider changing things a bit for the next version where I essentially rename the original SGDK makefile something else and make my wrapper the name of the original makefile.

That may make integration easier.

[Tim5000]

That would sound sensible to me, but as just a casual user my opinion may not be the best thing.
However as it was working with an older version that suggests a change recently (or just that mine was previous working by pure luck!) so there might be some merit in it.

Either way if you choose to close this I won't complain as at least anyone with the same setup as me should be able to get it working just by changing the configuration of the plugin so thanks for pointing me to the correct information.

FYI, it looks like the git repository for the VS Plugin is here.