I really don't know for sure but I doubt it. I'm also doing #include <mosquitto.h> but it does not imprint anything. My initial hunch is that json.hpp caches the path of the header file to use in some kind of debug prints or something. Could it be? Is there debug printing properties using the header name? I tested adding the header to multiple cpp files. Every inclusion = new header path in the final binary.

Can I do something to investigate?

I tried g++ -E single_include/nlohmann/json.hpp but did not find an absolute path to the json.hpp file in the output. I also called strings on some test binaries and also did not see a path there.

I made a simple test case in the beginning. Am I compiling it wrong? I'm using 2.1.1 which ships with Ubuntu 18.04.6 LTS.

user@MACHINE:~/repos/helloyoctoworld$ g++ --version
g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thank you! Making #define NDEBUG before header inclusion and undeffing it afterwards has taken the assert path away. I am quite confident that the builds will now be reproductible with different paths.

If you just want to get rid of asserts, you can add this before the include.

#define JSON_ASSERT(x)

Thank you!