In the book, "The pragmatic Programmer", there are several tips on how to manage code. One of the tips are "DRY"
It means "Don't Repeat Yourself"
Every time that the windows make sequence is altered, it breaks all the other makefiles. I find myself updating the linux mkefile every time. To this end. I'm going to research into autoconf. This shoud clear alot of the headaches.
However.
DevC++ is an issue. It's a Windows IDE. I'm probably going to create some scripts to parse the DevC++ files and auto-generate the m4 scripts for autoconf. This will add some dependencies to the application.
This incudes a need for autoconf and it's required subprograms (m4, imake, etc). Also support scripting will be done with ruby. (Many of you know ruby by it's popular web mod, "rails") <---- Ruby on Rails.
Just warning you, the make system is going to get "wierd" while I figure this thing out, at least on the non DevC++ side of things.