From owner-freebsd-newbies Mon Sep 24 22:50:45 2001 Delivered-To: freebsd-newbies@freebsd.org Received: from ocis.ocis.net (ocis.ocis.net [209.52.173.1]) by hub.freebsd.org (Postfix) with ESMTP id F2A1937B405 for ; Mon, 24 Sep 2001 22:50:41 -0700 (PDT) Received: from darkside (dial-216.ocis.net [209.52.174.167]) by ocis.ocis.net (8.9.3/8.9.3) with ESMTP id WAA14432; Mon, 24 Sep 2001 22:50:34 -0700 From: "Freddie Cash" To: Date: Mon, 24 Sep 2001 22:41:01 -0700 Subject: Re: help me understand: make, also file locks Reply-To: fcash@bigfoot.com Cc: "leegold" Message-ID: <3BAFB67D.30076.6F3624@localhost> In-reply-to: <001701c14580$6ab3e730$0201a8c0@shavedham> X-mailer: Pegasus Mail for Win32 (v4.0, beta 40) Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Coming from the ms world, i always installed programs > by pressing a button. i suppose the programs were in binary form. With > freebsd I often see the make command associated w/installing. if > someone could just briefly explain make, make install, and make clean? In a nutshell, the combination of make and the associated Makefile is like a more powerful, glorified batch file. The Makefile is simply a list of compilation, installation, deinstallation, deletion, etc commands. It also contains targets, which are simply sub-sections that include instructions for specific tasks (for example, install and deinstall). Makefiles and Windows Installation Scripts are very similar, although Makefiles are much more powerful. :) Have a look through some of the Makefiles included with various programs. Once you get past the seeming gobbledygook, you'll start to notice the general flow of the file and how it works. :) In FreeBSD, there are two ways to install a program: using ports, and using packages (okay, you can also install from source yourself, but it's not generally suggested). When you install a package, using the pkg_add command, the install works the same as in Windows: a script is read that copies the binaries to the right places and sets any initial config options. When you install a port, using the make command, you are doing the same steps as above, but you have to compile the source code into binary beforehand. The make command does all this for you (including downloading the source, checking any dependencies, compiling, and installing everything for you) according to the instructions included in the Makefile. Hope that clears it up a little for you. :) Cheers, Freddie fcash@bigfoot.com Linux is for people who hate Windows. FreeBSD is for people that like UNIX. -- unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message