Re: 4go/4gi format ?

Hiya all! Regarding my original post requesting info on the 4go/4gi file format for the purpose of creating a smart linker - Many people have suggested using Makefiles to handle the job, and one kind person outlined a perl script that scans the source files to find function definitions and references and produce a link script. We are currently already using automatically generated Makefiles. Our system has about 1500 source files spread over a directory tree with 165 directories and about 120 Makefiles. Scanning this number of source files to generate the Makefiles takes time and machine resources, especially if we regenerate the Makefiles frequently to keep the dependancies up to date. Even then, we have problems with changing library functions and partially invalidating the current dependancy lists during the course of a day. And yes, the Makefiles themselves can be made dependant upon the source files so they will automatically regenerate themselves (this is with GNU make) in response to changing source files. But most changes to the source files don't mean changes to the dependancy lists, so doing it this way creates unneccesary machine load. The good news. I now have enough (I think) of the 4go format to produce a proper linker. So now it's time for me to put my head down and beaver away. Thanks for the responses, both here in the newsgroup and email. Cheers -- Li-Chuan Dunlop -- s925095@minyos.xx.rmit.edu.au