On 5/21/25 14:44, Bruno Haible wrote:
I would therefore propose a more future-proof approach: based on the same approach as we have been taken for so many other .h files.
Yes that all should work. All I'm saying is that if that approach determines that the system <stdckdint.h> is fine (for both C and C++, assuming we're using C++ too), then Gnulib shouldn't replace stdckdint.h.
Partly this is so that people who are doing builds don't get confused by Gnulib interposing a no-op stdckdint.h.
