saxbophone

> The case is the following: Tests are disabled in Release mode, and they are enabled in Debug mode. But user can change the behavior by passing the option ENABLE_TESTING....

> @saxbophone , Is it hard? No, I've just been busy doing other stuff and haven't got round to it yet. You will be able to see when I start...

> Somebody lies on the Internet again... You know, I really was going to do this for you when I found the time for it, but if that's your attitude...

> Do you want to make a PR to add such a messaging? Alas, I would but I've had a look at the documentation codebase and I'm a little lost...

> so we're just trying to be transparent with the additional documentation. Talking of which, did you end up documenting this requirement additionally in the "compiling from source" section, as...

> The tutorials are really just HTML, the PHP at the top and bottom can be ignored, nothing exotic to grok 😀 Ahhhh! Good to know, I thought it was...

> Well, if it's part of the documentation, then yes, it's generated, you'd have to edit the C++ code. But the tutorials are HTML sprinkled with a bit of PHP...

Also, remove -Wdocumentation warning flag, because it's dodgy (inconsistent with Doxygen)

> Do you actually still need libfuse on OSX? There is https://osxfuse.github.io/? > It looks like macFUSE is stuck at implementing just the 2.9.7 API of libfuse only: https://github.com/macfuse/macfuse/issues/390

> Sorry, I actually meant https://www.fuse-t.org/ Ah cool. It looks like that one's a little behind the libfuse API too, but thanks for signposting me towards a hopefully more stable/maintained...