search for: __config_site

...and $prefix/lib as today. > > > > Once the overall scheme is agreed upon, we could also consider > > de-duplicating C++ headers across targets, by moving shared headers into > > a common directory, with only varying subset in include/$triple. > > At the very least the __config_site headers cannot be de-duplicated. > I think it should be sufficient to have separate __config headers for separate targets, that's really the only thing that differs. > Beyond that, I strongly disagree with de-duplicating them in general > because it will break --sysroot= unless you...

Today, there're two different locations for runtimes files within Clang's installation: compiler-rt: headers: $prefix/lib/clang/$version/include(/sanitizer) libraries: $prefix/lib/clang/$version/lib/$os/libclang_rt.$name-$arch.$ext libc++, libc++abi, libunwind: headers: $prefix/include/c++/v1 libraries: $prefix/lib/$name.$ext The scheme used by libc++, libc++abi, libunwind

...y. >> > >> > Once the overall scheme is agreed upon, we could also consider >> > de-duplicating C++ headers across targets, by moving shared headers into >> > a common directory, with only varying subset in include/$triple. >> >> At the very least the __config_site headers cannot be de-duplicated. >> > > I think it should be sufficient to have separate __config headers for > separate targets, that's really the only thing that differs. > > >> Beyond that, I strongly disagree with de-duplicating them in general >> because it...