Why 2.02 instead of 2.05?

Now that the problem is solved, can i please hijack this one? C, masm and windows had been my job before i retired, i have never had a chance to work with gcc. DOS, djgpp and rhide is my new hobby. How the hell do you make the linker stop pushing object duplicates when working with multiple c and header files? Is there a flag for that? I am using rhide and "build all" never works, i need to compile c files one by one, and link them manually, occasionally it also nags about forwarded structs. Rhide also somehow forgets about key bindings, and has some other issues, but i can live with that. What am i doing wrong? Its not that I not aware of guard defines or header files logic.

EDIT:
Solved, apparently header files should not be added to the "project", only c files (and keep h files in the same folder). I got used to IDEs that list header files along c files and name that a project, djgpp is different.

You're really doing yourself a disservice by sticking to the ancient release of djgpp on Dos. If you used the cross compile djgpp toolchain on a modern Windows, Linux or Mac system you would get the advantage of a far better compiler and the ability to plug it in to most modern IDE or editors (if you want to hat sort of thing).

Of course, since it's just GCC with a standard C library and some custom crt's, you really don't need an IDE at all. A makefile and a text editor works just fine.

GCC should only include the symbols that your code requires. But it won't automatically fix duplicate definitions for you - ensure your headers include the correct include guards for that.

Azarien wrote on 2023-04-18, 20:31:

Why 2.02 instead of 2.05?

Cuz it's a part of my environment to build Boom 2.02, MBF 2.04 and Tartar