Re: [Further-devel] FreeBSD build tweaks

From: Richard Clamp (
Date: Sun Jan 27 2002 - 16:39:04 PST

On Sun, Jan 27, 2002 at 04:15:18PM -0800, Evan Martin wrote:
> On Mon, Jan 28, 2002 at 12:00:44AM +0000, Richard Clamp wrote:

> Ack! I probably just introduced this in the latest changes. Is there a
> FreeBSD-compatible way of parsing command-line options? I don't mean to
> introduce dependencies (the command-line options right now are all
> debugging-related).

I don't really know, but gnu getopt is trivial to install, and from a
quick check 85 other packages in the ports tree depend on it too.

I suspect it's not really worth expending the extra energy, and
sticking ugly ifdefs through the code, just to avoid an extra
dependency (though my machine is still chewing through building enough
of gnome to make sawfish happy).

> > the Makefiles also expect GNU make, so install the gmake package
> > cd /usr/ports/devel/gmake && make install
> That may be unavoidable. I don't know how different GNU make is from
> FreeBSD make... it seems I'm not doing anything too strange in the
> Makefiles, but I was raised on GNU...

I'll take a look later on if I can I hunt out my copy of the make book
there are traditional ways to do most of the newer gnu tricks. By the
same metric for getopt, 1333 packages want gnu make, so it's also not
that much of a problem, and easier to fix via documentation.

> > -CFLAGS=-g -Wall `evas-config --cflags`
> > +CFLAGS=-g -Wall `evas-config --cflags` -I/usr/local/include
> Is this to pull in the getopt headers?

Yup, and those of X if you built it from a port, so on and so forth.

> Thanks again! I'm sorry the code is so messy... lemme know if you have
> any further (heh) input.

Not a problem I'm always glad to produce patches, especially as I'm
building on someone else's efforts. Messy code can always be patched
into cleanliness, it's a little trickier to patch nothing into
something though.

Richard Clamp <>

This archive was generated by hypermail 2.1.4 : Tue May 28 2002 - 23:37:04 PDT