Slavko Kocjancic <esla...@gmail.com> said: > > > So what is correct way? just "make" ? > > > > > Yes, 'make' is enough > > > ... but how "make" know that I make change on some file? I suspect that I > should tell what file I changed?!?
make has to know that the file you are editing is part of the source code to be compiled. Once it knows that, it looks at the timestanps of the source code and any binaries (FILE.o, SOME_LIB.a or exicutable). If the source code has a modification time newer than the .o file, it knows to recompile just that piece. Put another way, the executables have *dependencies* of a bunch of compiled pieces. Ech of these compiled pieces depend on a piece of code in a separate file. When the source file is updated it triggers it to be recompiled, and then the executable gets re-linked. These Make tutorials might help explain the details: http://www.opussoftware.com/tutorial/TutMakefile.htm http://mrbook.org/tutorials/make/ Hope that helps, EBo -- ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
