Re: [Dri-devel] latent Xaw dependency

[Robert F M. <gr...@t2...>]

ajax wrote:

>xc/programs/Xserver/hw/xfree86/xf86cfg/accessx.c has a dependency on Xaw:
>
>#include <X11/Xaw/Command.h>
>#include <X11/Xaw/Form.h>
>#include <X11/Xaw/Label.h>
>#include <X11/Xaw/Scrollbar.h>
>#include <X11/Xaw/Toggle.h>
>...
>
>There's an xc/lib/Xaw directory in CVS but it's empty, which means the user 
>needs to have the Xaw headers installed already.
>
>accessx.c is part of xf86cfg.  Is there any reason for us to build any 
>programs besides glx{gears,info}, xdriinfo, (maybe) the server binary itself?
>
>There's several ways to fix this obviously, either bring back the Xaw headers, 
>stop building useless binaries, or just document the need for the headers on 
>the Building page.  #3 is probably easiest.
>
>- ajax
>
>
>-------------------------------------------------------
>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
>Dri...@li...
>https://lists.sourceforge.net/lists/listinfo/dri-devel
>
>.
>
>  
>
Why do we need to build glxgears and glxinfo? And is the server binary 
really necessary?
Why do we build libexpat and libfreetype? libxdmcp, libXv?