Hi Renato, One important behavior common among the make tools is the fact them > make a compilation of only a few modules that have changed. From what > I read recently in this list hbmk2 tool not have this behavior and > you do not want to implement this feature, am I right?
Yes, this is right. > If this is true, I would like to know if you can at least include a > parameter in hbmk2 to prevent he from deleting the temporary files in > the output of the program. > > Explain: I am outlining an auxiliary tool that will work with the > hbmk2 to compile only the changed files, but I can not use it because > these files are always deleted. > > If .C / .O[BJ] / .RES are not erased, then I could compile only the > changed files... > > what do you think of this idea? hbmk2 implements -hbcmp and -hbcc switches which you may find useful for this purpose: '-hbcmp' will stop after calling Harbour compiler, so it will produce .c files. (but you probably don't need this for an incremental make to work). '-hbcc' will stop after calling C and resource compilers, so it will produce .o / .res files. hbmk2 will also accept .o, .res files as inputs. With these capabilities you can use it with incremental make tools. > [ I even did a function that detects when a file needs to be or not > compiled into hbmk2 ... so then I believe that one tool can be more > useful.] Useful, no question about it, but this would mean replicating the job existing tools, and probably a lot more time investment that it first seems. We will see, maybe this can be done cleanly and simply and someone will do it, but by now I'd like to test hbmk2 to be stable with current features. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
