Date: Tue, 8 Oct 1996 23:54:27 -0700 (PDT) From: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu> To: rhwang@bigpanda.com Cc: ports@freebsd.org Subject: Re: [Q]: How to handle ports which have optional X Windows components? Message-ID: <199610090654.XAA07942@relay.nuxi.com> In-Reply-To: <199610090146.VAA00761@megazone.bigpanda.com> from Richard Hwang at "Oct 8, 96 09:46:24 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm currently porting jed and friends (slrn and slsc). Jed has an > optional X Windows version called xjed. What is the best way I can > detect X so I can take the appropriate action in regard to compiling > and installing xjed? USE_X11 doesn't seem to be what I'm looking > for. I'm looking for some way to determine whether X11 exists on the > system, and if so, pass the info to 'configure'. Any suggestions? I've been struggling with this one over vim/gvim. My latest try is in freefall.freebsd.org:/incoming/vim44-port.tgz. You can also see the vile/xvile ports. It is easy to detect if X11 exists on the system you are building on. The big problem is the *package*. If Satoshi/JHK is using X11 on the build machine (highly likely), then your port build your port with X11. If some poor user w/o X11 installs the package of your port, then it wont work for them. At this point, I belive I will have two ports vim and gvim. I've been burned by the package wanting X11 when I was installing on a small box w/o the RAM for X11. -- David (obrien@nuxi.com)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610090654.XAA07942>