On Wed, Mar 17, 2004 at 09:07:12AM -0800, Jon Smirl wrote: > --- Alan Hourihane <[EMAIL PROTECTED]> wrote: > > I'd also like to mention that the Imakefile's or Makefile.linux/bsd will > > still need to be in some form in these three directories. > > > > xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel > > xc/xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel > > xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel > > > > The reason being is that this new drm module is more than likely going > > to get imported into... > > > > xc/extras/drm > > > > and then symlinked into the original directories with the Imakefile during > > the XFree86 build process. > > Please don't do the individual file symlinking again. It makes the build process > very fragile. For example if I add a new include file to the drm project > individual symlinks will make me need to patch up the Imakefile file in all of > the dri branches. Linking directories is ok. > > The changes I made to mesa impacted all of the dri branches because of the > individual symlinks. The Mesa tree is external to the dri tree; dri branches do > not insulate you from external changes. Directory symlinks are better at > isolating things. With directory symlinks addition of a new file doesn't break > things. Of course if we add a new directory things will break again. > > The best isolation is a single symlink to the top of the external tree and then > use makefiles that are stored in the external tree.
May I suggest you provide an Imakefile that does what your suggesting ? Alan. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel