[ My appologies for my previous message with no body.  It was a local
  mail client burp. ]

I want to build XDirectFB.  But my quesion is, is building XDirectFB
mutually exclusive of building XFree86 for native display hardware?

To explain a bit further.  I have an XFree86 source rpm file.  It is
used to build a set of XFree86 packages that have hardware drivers for
the array of hardware that XFree86 supports.  Other than a bunch of
patching and enhancements (like additional hardware support, font
support, etc.) , it builds a host.def file and then runs make World.

Can I simply "add" to this build so that directfb is just another
"hardware module" or would I have to have a separate build that built
an XDirectFB-only XFree86 package?

I am currently doing a test build (no XDirectFB modifications yet) of
the SRPM to make sure it's good but once that is done, I want to try
building the same XFree86 packages, with the directfb module included.

I have modified the SPEC file to apply the patch, and put the
requisite hw and config files in place.  It also adds:

  #define XDirectFBServer YES

to the bottom of the host.def file.  Will this cause the XFree86 build
to build the directfb "hardware module" in addition to all of the
others it would normally build for an intel86 environment or is this
just not going to work the way I am hoping it will?

Once this is all done, is it simply a matter of changing the
XF86Config-4 file's "Device" Section parameter "Driver" to "directfb"
to get this all working?  Or am I totally missing the mark here?

You might ask why I am going to all this trouble to get XDirectFB to
build with an existing XFree86 RPM.  Ideally, I would like to get my
Linux distro vendor (Mandrake) to accept all of this DirectFB stuff
into their distribution and continue to support it as new releases
happen (and I don't have to continue to maintain it here on my boxes).
Being able to support XDirectFB with their existing XFree86 packages
would go a long way to convincing them that this is a good thing, or
benign in the least.

Thanx,
b.

-- 
Brian J. Murrell

Attachment: msg01258/pgp00000.pgp
Description: PGP signature

Reply via email to