Well, in linux makefiles are used with the program "Make" to compile software. I'm pretty sure the makefile contains a list of directions on what is required and how to compile the software. The .bak extension...tends to mean its a backup...as in the makefile was modified and replaced with a newer one. Hopefully this explanation applies to what you're doing.
So lets assume there's source code and a MAKEFILE. What command(s) do I need to do to compile? There also seems to be a makefile.exe in another directory but the ms-dos shell didn't like it when I ran it. I tried PSYMAKE ALL and I got some errors. Who's good at this stuff?
well in linux I would type if the makefile is named just makefile: make if it has some other name, like in your case makefile.bak make -f makefile.bak also you should check makefile.exe in notepad to see if is just a strangely named makefile or if it's a real executable. if it's a exe file maybe you should use it with the makefile?
Just the makefile is no use. It would have to be all the files. I understand that usually people don't like to do this, but my time is more expensive than any prototype & helping people build things you will never see is no fun. smf
Assuming I got the code to compile and work on a development board, how would I put this on a disc so that everyone could boot it up?
the instructions in here for main method 2 should work. http://www.zophar.net/tech/files/thepsxdoc2.txt I normally use different software to that, but it should get you going. smf
Ugh. I'll try this. Thanks. I see mention of a CTI file. I think somewhere in the source I have backup of there was a CTI file as well. I might have to look in on what it is and what it does.
