build Xorg with read-only source tree

Egbert Eich eich at
Tue Apr 25 03:26:26 PDT 2006

In principal this is possible to do without lndir in an autotooled
environment. Create an empty dir for buidling, cd there and call
configure in the read only source dir. ie:
mkdir foo
cd foo

This however requires configure and the .in files to be present - which
isn't true for sources directly pulled form cvs or git as we don't keep
these files in there. 
Thus you will have to call (or better 'autoreconf -v --install' 
as does too much )in the source directory at least once.

If you want to ensure that your source directory stays clean of any 
derived files however you should go the lndir way.


Felix Kühling writes:
 > The traditional way of doing this is using lndir. For me this still
 > works with the modular tree, though I have only tried it with a handfull
 > of modules. The source is in util/lndir in the modular tree. I'm using
 > it for the DRI snapshot builds so that I can create a clean build tree
 > each time without having to re-checkout or copy the entire source tree.
 > Regards,
 >   Felix
 > Am Mittwoch, den 15.03.2006, 19:30 -0800 schrieb Jeremy C. Reed:
 > > What is the best or easiest way to build the modular Xorg with a read-only 
 > > source tree?
 > > 
 > > I will be sharing the source tree for different platforms (via NFS) and 
 > > want the built files to be in their own (per platform) directories.
 > > 
 > > I have been using
 > > 
 > > Thanks,
 > > 
 > >  Jeremy C. Reed
 > > 
 > > p.s. I plan on testing the XCB-based libX11 for NetBSD now.
 > > 
 > > 
 > > _______________________________________________
 > > xorg mailing list
 > > xorg at
 > >
 > > 
 > -- 
 > | Felix Kühling <fxkuehl at>            |
 > | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3  B152 151C 5CC1 D888 E595 |
 > _______________________________________________
 > xorg mailing list
 > xorg at

More information about the xorg mailing list