On 08/11/2007, michael schuster <Michael.Schuster at sun.com> wrote: > Shawn Walker wrote: > > > Perhaps a better way to do this is to check for the presence of a tool > > that we could build first, and failing to detect it, building and > > installing it. > > > > Now how we want to do that is up for suggestion... > > something just occurred to me - if this has been discussed already, excuse > an often distracted hanger-on ;-) > > we must make sure that we don't repeat the trap gnu configure leads into, > ie. confusing the *build* machine with the *run* machine. I'm fairly > certain the move to cmake has taken care of most of this, but I want to > make quite certain that the scheme Lukas suggests doesn't affect the > installability of the resulting stuff on other machines.
I was always under the impression that what this kdebld installs should not be depend upon by what we build with it to install on a target system; if that's what you mean. -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "We don't have enough parallel universes to allow all uses of all junction types--in the absence of quantum computing the combinatorics are not in our favor..." --Larry Wall
