If you use lndir to make a build tree then the XDarwin.app that gets installed by 'make install' is broken. [n8gray@golux MainMenu.nib]$ pwd /Applications/XDarwin.app/Contents/Resources/English.lproj/MainMenu.nib [n8gray@golux MainMenu.nib]$ ls -l total 0 lrwxr-xr-x 1 root admin 103 Dec 21 18:38 classes.nib -> ../../../../../../../../xc-cvs/ programs/Xserver/hw/darwin/bundle/English.lproj/MainMenu.nib/classes.nib lrwxr-xr-x 1 root admin 103 Dec 21 18:38 objects.nib -> ../../../../../../../../xc-cvs/ programs/Xserver/hw/darwin/bundle/English.lproj/MainMenu.nib/objects.nib Needless to say, these symlinks don't work and XDarwin can't start. This is X.org 6.8.2 RC1 built with an lndir source tree on OS X 10.3.7.
Assigning to me as this is a Darwin specific build issue. Solutions are: 1. Have Apple modify Xcode to add an option to follow symlinks in assembling application bundles. I filed a bug/feature request with them for this awhile ago. I'm not holding my breath. 2. Stop using Xcode to assemble the application bundle. The requires teaching Imake or some other build system in the modular tree to be able to make application bundles. This is a bit of a moving target since the X11 build mechanics are in flux.
I wanted to use lndir as well to prepare the build and noticed lndir is provided by xorg, so people who don't have xorg installed can't use lndir. Not to terrible. I compile it first as follows: cd $BUILDDIR sed -e 's|X11/Xos|string|;s|X11/Xfuncproto|unistd|' \ $PKGMK_SOURCE_DIR/xc/config/util/lndir.c \ > lndir.c gcc lndir.c -o lndir ./lndir $PKGMK_SOURCE_DIR/xc rm lndir* Perhaps it's an idea to replace the X11 headers in lndir like I did, so people can build it without having to have x11 installed.
Is this still an issue using a current version of xorg?
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
no longer an issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.