One problem I have run into time and time again with make is using the wrong version. If you have Borland C++ Builder installed on your machine, it's possible you may have a make entry in your path statement already, but to the wrong make! - I always create batch files in each applications folder I create along the lines of:
My build batch file, click on this to build your gxb using make
cd c:\devkitadv\code\pauls
c:\devkitadv\bin\make
start c:\devkitadv\gpee32\geepee32.exe /GXB=c:\devkitadv\code\pauls\pauls.gxb /RUN
Then I have a make file as follows, funnily enough called "makefile", no extention:
# devkitadv base dir
export CCBASE=c:/devkitadv
# User options passed to the compiler
export CUSER=-DLITTLE_ENDIAN -DGP32
include $(CCBASE)/gp32.mk
#------------------------------
all: pauls.gxb
pauls.gxb: pauls.elf
pauls.elf: paulmain.o
$(LINK)
paulmain.o: paulmain.c
clean:
rm -f pauls.gxb pauls.elf paulmain.o
and that's it. It means that I don't have to include make in my path statement what-so-ever. I am sure most people would hate this method but when you have Borland C++ Builder, Microsoft Visual C++ Studio, Borland free compiler, DevKitAdv all running under one roof, I find it the easiest method.