lib/clang/3.4 -> lib/clang?

In the install directory, can we remove the clang version from the
path to the runtime libraries?

Thanks,
Greg

In the install directory, can we remove the clang version from the
path to the runtime libraries?

Er, no? How would you install two versions of clang side-by-side?

(Note the binary name also has the version in it...)

The Unix-y style is to scatter relevant bits across unversioned top-level directories (/usr/bin, /usr/include, /usr/lib) and so version-specific stuff needs to be segregated underneath somehow, typically with a versioned path name (e.g. lib/clang/3.4 or whatever).

To avoid that you’d need to package everything associated with a given Clang version in one subtree underneath a versioned directory (e.g. /clang/3.4/bin, /clang/3.4/include, or something along those lines). This doesn’t actually eliminate the versioning issue, it just moves it, but depending on your environment that might well be preferable and/or more convenient.

I can’t imagine you’d get any traction trying to change that on the Unix-y platforms though.

–paulr