On Wed, Apr 09, 2008 at 01:35:06AM -0600, Connor wrote:
> Hi,
> 
> I'm running 4.2-stable on i386 and was wanting to turn on some
> configuration options (for specific subpackages) that are turned off
> by default when one runs builds xenocara using the vanilla process in
> the /usr/src/xenocara/README file and the FAQ.
> 
> I checked out the stable source for xenocara and it builds and
> installs successfully by following the usual procedure:
> 
> # cd /usr/src/xenocara
> # make bootstrap
> # make obj
> # make build
> 
> I made sure that I installed the additional GNU autotools packages
> that are listed in the README, and /usr/X11R6/bin is in my PATH .
> 
> I have a specific example of something I'd like to modify: I'd really
> like to change some of the options for app/xterm, say to enable 256
> color support, which is turned off when doing the default build.
> 
> If I were running the configure script manually I could do the
> following in app/xterm, for example:
> 
> #cd /usr/src/xenocara/app/
> #sh configure --enable-256-color
> 
> (which should enable that option)
> 
> I'm not sure that that will get picked up properly when I do a make
> build though.

probably not.  and I doubt your example works as expected.  here's
the first cvs log entry for xenocara/app/xterm/Makefile

revision 1.1
date: 2007/04/09 19:11:43;  author: matthieu;  state: Exp;
BSD make based build infrastructure for xterm. The autoconf based
one was too painful to get working on landisk (static only).

so, xterm build doesn't even use configure ...

> What is the proper way to set things up so that the xenocara wrapper
> scripts know to turn on those non-standard options?
> 
> Any recommendations would be really appreciated.

three answers:

1) this isn't supported.  I mean, even ports don't allow you to
do stuff like this, because, well, you would be using a non-standard
build, which is untimately useless, if not actually detrimental, to
the project. that being said, there are a few build options for base
and xenocara, see mk.conf(5).

2) look at /usr/xenocara/share/mk/bsd.xorg.mk, particularly where
it's running configure.

3) as you can see in the xterm example, not everything in xenocara
uses configure.


> Thanks,
> 
> Connor
> 

-- 
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org

Reply via email to