config.h vs. xorg-config.h

[Thomas Winischhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


In order to implement randr-rotation support into the sis driver, I will
have to implement a driver-internal replacement for shadowfb.

Now I looked at shadowfb/shadow.c and noticed it starts with

#ifdef HAVE_XORG_CONFIG_H
#include <xorg-config.h>
#endif

as opposed to driver source files, which do

#ifdef HAVE_CONFIG_H
#include "config.h"
#endif

shadow.c includes some headers from the guts of the server, like mi.h,
windowstr.h, dixfontstr.h, which I also will need in my internal
replacement.

So, what about the config.h-include?

Will this all cause problems with the modular tree as it stands now?

Thomas

- --
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net	       *** http://www.winischhofer.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDORy8zydIRAktyUcRAhFOAJ9oJAa5k0OEVLHKxPdqDvV0SpFtaQCfY6VJ
AS5miUZIJeZYODRmN4PO8+g=
=28Vi
-----END PGP SIGNATURE-----