[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Using build.sh for cross builds
On Mon, Feb 15, 2010 at 11:24:47PM +0200, Alan Barrett wrote:
> > In our environment, the desire is to build the tools once, keep them
> > on a read only mounted file system. Tools only updated when needed
> > for everyone. I believe at one time I read that there was a flag to
> > inhibit (re)building tools.
> Wow, a read-only TOOLDIR! I haven't heard of anybody else trying that,
> and it's outside the intended scope of build.sh, but I expect that it
> would not be too difficult to make it work. I don't have time to work
> on it now, but if you can make it work and submit patches, then I am
> sure there would be some interest in getting them committed.
Isn't there an option/setting/something for skipping the tools build
completely from build.sh? I think it's underdocumented intentionally
to discourage people who don't know what they're doing from using it
and getting in trouble, but I think it does exist. Using that should
make read-only tools work fine.
David A. Holland
Main Index |
Thread Index |