On Wed, Jun 11, 2025 at 10:25 AM Branko Čibej <br...@apache.org> wrote:
> On 11. 6. 25 06:21, Nathan Hartman wrote: > > (snip) > So that's obviously something to be fixed. I wonder why this particular > #include in this specific place? After all, we're including other APR > headers elsewhere. > > > > I'll explain for the fifth time: apr_xlate.h is an apr-util header, not an > apr header. cmake links include directories with the properties of a > target, in this case, the apr-util library. So the include path is there > when it builds any of our code that explicitly *links* with apr-util – it > gets that knowledge from our build.conf – but not in cases where our code > just *includes* that header (via svn_utf.h), without linking with > apr-util. The build.conf file doesn't say anything about that, clearly > because it expects all include paths to be available for compiling all our > sources. > > Ah yes, *now* I remember seeing this discussed before. Ack. Cheers, Nathan
