Not to make too big a deal of it, but the idea was that if you went out of your way to define DRM_FOURCC_STANDALONE in your code base, that you would also go through the pain of removing drm.h includes elsewhere. It's too annoying of an implication to document/communicate, so I'm happier with the other DRM_FOURCC_STANDALONE solution that pulls the basic types into a common header.
Thanks, James On Mon, Dec 7, 2020 at 1:49 AM Simon Ser <cont...@emersion.fr> wrote: > On Monday, December 7th, 2020 at 9:57 AM, James Park < > james.p...@lagfreegames.com> wrote: > > > I could adjust the block to look like this: > > > > #ifdef DRM_FOURCC_STANDALONE > > #if defined(__linux__) > > #include <linux/types.h> > > #else > > #include <stdint.h> > > typedef uint32_t __u32; > > typedef uint64_t __u64; > > #endif > > #else > > #include "drm.h" > > #endif > > This approach still breaks on BSDs when DRM_FOURCC_STANDALONE is defined > and > drm.h is included afterwards. >
_______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
