Better docs or features for intermediate-complexity use cases (nested headers)

I'm following the instructions for using libbindgen in build.rs, and I'm trying to generate bindings for a c library that uses glib. This example doesn't seem to quite meet my needs because glib headers assume an include path for headers they then include, and adding the subheaders to my wrapper.h I think it thinks #include <glib-2.0/glib/gmacros.h> is different from glib/gmacros.h. Or anyways, it's not working. glib assumes users just include the top-level glib.h.

Then I can look at Servo's use of bindgen for Stylo, and how it's recursively finding includes, but it's also doing a lot of other stuff so "just make bindgen handle includes recursively" isn't easy to extract from that for my project. Nested includes and include paths are something that almost every C lib that has more than one header does, so more docs or moving this capability into base bindgen would help a lot, I think.

Start with the libbindgen instructions used from build.rs and the wrapper.h setup described in the issue. Compare them with Servo's Stylo bindgen usage, then define whether the result should document or support recursive nested includes and include paths for glib-like headers; done means the intended approach is clear and works for that use case.