Sorry, I always forget.

Here's an example.

When viewing the file page, I see meow.h File Reference at the top. I'd like to see common/meow.h File Reference.

Or something automaticaly generated in the description like:

#include "common/meow.h"

Doxygen version is 1.13.2.

Is this possible?

In the end I want to show what exactly my user needs to include to use what that specific file offers. Manual pages of functions and types often show this: see read(2) for example.

You're right: it's not obvious from my minimal example alone which doesn't match my real use case, therefore in this case we can rely on the tree on the left to deduce that meow.h is within the common directory.

Here's an updated one.

Now, the file is part of the salut topic, and its page will show under the "Topics" section of the left tree, hiding the common directory:

I know you can still see the common directory here:

But when you're on the meow.h page, I want you to know what to include to be able to use the API of that file, therefore I'd like the title to include common, like this:

(See the updated left tree too).

My solution so far is to manually add the include code to the file description: