Date: Thu, 18 Nov 2004 19:11:03 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> Cc: freebsd-questions@freebsd.org Subject: Re: BSD equivalents of autoconf, automake, etc. Message-ID: <20041118171103.GA61117@orion.daedalusnetworks.priv> In-Reply-To: <20041118165953.GA46467@dogma.freebsd-uk.eu.org> References: <20041118160531.GA43779@dogma.freebsd-uk.eu.org> <20041118101808.11092f21@dolphin.local.net> <20041118163221.GB45289@orion.daedalusnetworks.priv> <20041118165953.GA46467@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2004-11-18 16:59, Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> wrote: > On Thu, Nov 18, 2004 at 06:32:21PM +0200, Giorgos Keramidas wrote: > : The minimal Makefile for building a program in FreeBSD looks something > : like this: > : > : PROG= foo > : > : .include <bsd.prog.mk> > : > : I can't even begin to describe all the 'make magic' that is hidden in > : /usr/share/mk/*.mk, but you can find out most of it by reading the > : comments in these make(1) include files. > > This is exactly what I needed. I wanted to experiment with building, > installing, linking, and the same with my own test 'libraries.' It looks > like this is much easier than autoconf. I usually copy stuff from the infinite pool of examples that /usr/src can be. For building a library, I jump in /usr/src/lib/libfoo and skim through a couple of Makefiles. After a while, you'll get the hang of it and write all you need without looking at the `samples' :) I got so used to working in the bsd.*.mk paradigm, that when I had to build a Solaris kernel module for a system that uses GNU make, I wrote a make include called sunos.kmod.mk and then started writing in Solaris stuff like this: $ cat sunos/modules/foo/Makefile KMOD= foo SRCS= foo.c fooddi.c foobar.c include sunos.kmod.mk $
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041118171103.GA61117>