On Mon, 2010-03-29 at 23:06 +0200, Slavko Kocjancic wrote: > > > 2010/3/29 Alexey Starikovskiy <[email protected]> > Slavko Kocjancic пишет: > > > > > > 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" is a program that can automate the compiling process. In a terminal session (Applications / Accessories / Terminal), type "man make" to get the make manual page. make uses a makefile that should be used to tell make what to do. For instance "make install" uses the install portion of the makefile. The only bit that I have learned, is it is common to install new software by using ./configure, make, make install. This runs a program called "configure" from the current directory, then runs the default portion of the makefile, then the install portion of the makefile. I think the default for make and configure is to use the current directory to look for the supplementary files they need. This is about all I know about make and I guessed on some of it, so check out the man page to get a better understanding. This may give you enough may be able to write your own makefile or at least see what other makefiles will do. -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
