[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-stable
Subject:    Re: cvsup
From:       Mike Meyer <mwm () phone ! net>
Date:       1999-09-03 17:32:04
[Download RAW message or body]

On Fri, 3 Sep 1999, Sheldon Hearn wrote:
:->On Thu, 02 Sep 1999 23:06:39 -1000, "Art Neilson, KH7PZ" wrote:
:->> in the future, how do I just update my sources with cvsup changes
:->> and only recompile those sources affected?
:->You either look at the output of cvsup -L 2 and update the affected bits
:->by hand, or you ``make world'' if you're as lazy as the rest of us.
:->There's no automated mechanism for only building updated bits.

The easy way to "update of the affected bits by hand" is to just do a
"make" - but you have to know what you're doing! The point of doing
the "world" makes is that you get the correct set of includes &
libraries. Those are the only build mechanisms that are supported.

I've found that deleting the /usr/obj tree before doing a buildworld
makes it run faster. Buildworld walks that full tree twice - once to
change flags, and once to delete it. Doing the full tree once and the
things that don't delete because the flags are wrong twice is faster.

:->> do I make update or just make or what?
:->
:->No. The update target is just a mechanism to allow you to update your
:->source tree conveniently. It's not much more convenient than running
:->cvsup, and you'll need to play with settings in your /etc/make.conf to
:->make it work. Probably not worth worrying about.

Make update can be set up to get both the soures and the ports
collection. As such, I think that's worth doing.

	<mike




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

[prev in list] [next in list] [prev in thread] [next in thread]