wallis@labc.enet.dec.com (Barry L. Wallis) (12/30/90)
In article <6232@videovax.tv.tek.com>, dougs@videovax.tv.tek.com (Doug Stevens) writes... |> |>I have used both MAKE with TCC and project-make within TC. The project |>make appears to be MUCH (much, much ...) faster. I speculate that the main |>difference is that when running MAKE, TCC must be re-loaded every time that |>a dependency triggers a compilation, and that TC loads the compiler only once |>before checking dependencies and compiling. |> |>I also prefer the project make because I don't have to maintain dependency |>lists in the makefile (even with automated tools, such as Polymake, you have |>to remember to run the tool to update the dependencies). |> Turbo C++ needs *lots* of memory. I used to think MAKE was slow until I found the -S switch. This switch swaps MAKE out while executing commands (significant memory saver). Also, using the -Qx switch on the compiler helps if you have extended memory (-Qe is the default if you have expanded). Also, running MAKE underneath the IDE (using the DOS shell command) will severly limit compilation performance. Don't forget the -a switch (or .AUTODEPEND directive) to tell MAKE to automagically check the .OBJ files for dependencies. --- Barry L. Wallis USENET: wallis@labc.dec.com Database Consultant Prodigy (don't laugh): DNMX41A U.S. DECtp Resource Center DECUServe: EISNER::WALLIS (not on the net yet) Los Angeles, CA "No one voted for me, I represent myself" ---