On Wed, Apr 9, 2008 at 9:35 AM, Connor <[EMAIL PROTECTED]> 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. > > What is the proper way to set things up so that the xenocara wrapper > scripts know to turn on those non-standard options?
Makefile.bsd-wrapper uses the CONFIGURE_ARGS and CONFIGURE_ENV macros, like in ports. For a particular module that's using a Makefile.bsd-wrapper file , you can add stuff to those macros: CONFIGURE_ARGS+= -enable-your-favourite option But, as Jacob already told you: 1) It's not supported and you'll be on your own if things don't work as expected 2) Not every module uses configure (xterm for instance already got converted to a more traditional BSD Makefile (in this case it was to overcome some limitations in xterm's configure script wrt static only architectures).
