[cfe-dev] lib/clang/3.4 -> lib/clang?

[Robinson, Paul]

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

From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On Behalf Of Chandler Carruth
Sent: Friday, November 01, 2013 12:56 PM
To: Greg Fitzgerald
Cc: Clang Dev
Subject: Re: [cfe-dev] lib/clang/3.4 -> lib/clang?

On Fri, Nov 1, 2013 at 11:48 AM, Greg Fitzgerald <garious at gmail.com<mailto:garious at gmail.com>> wrote:
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...)


Thanks,
Greg
_______________________________________________
cfe-dev mailing list
cfe-dev at cs.uiuc.edu<mailto:cfe-dev at cs.uiuc.edu>
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20131101/2a040520/attachment.html>