Installing/Distributing Binaries After Modular Build

[Jeremy C. Reed]

On Thu, 18 Jan 2007, Barry Scott wrote:

> Jeremy C. Reed wrote:
> > On Tue, 16 Jan 2007, George McCollister wrote:
> > 
> >   
> > > I'm using build.sh to build the modular source tree. The wiki suggests
> > > setting
> > > the prefix to /tmp/modular. What did the author intend to be done after
> > > everything is built? Permanently running X from /tmp/modular doesn't seem
> > > acceptable.
> > >     
> > 
> > I think that is just an example. Not a good one.
> > 
> >   
> > > If I git the source tree to /home/georgem/X11R7.1 and build
> > > everything under my user, what is the suggested way of installing
> > > everything
> > > as root to a normal location? build.sh seems to create tar balls for each
> > > module, but they only include source. Is there a way to build binary tar
> > > balls
> > > (or packages) for each module that can be used to install to a different
> > > location or used on a different system.
> > >     
> > 
> > Use DESTDIR for each separate component and then tar up that directory it
> > creates to make separate tarballs of the binaries.
> >   
> Each component uses the header files from /usr. You cannot, to my knowledge,
> tell configure where you are staging the kits so that you leave /usr
> untouched.
>
> This means that after building each component you must install it into /usr.
> You can also use DESTDIR to make a kit for a single component.

That is right you do need the dependencies installed. I said basically the 
same thing in the email you replied to but you clipped it out.
 
> You also have to get Mesa built at exactly the right point in the Xorg build
> sequence. Mesa depends on Xorg files and Xorg server depends on Mesa.

  Jeremy C. Reed