[cfe-dev] Renaming the install-clang-headers target

[Dimitry Andric via cfe-dev]

On 22 Feb 2019, at 03:44, Tom Stellard via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> 
> On 02/21/2019 03:56 PM, Shoaib Meenai wrote:
>> Thanks. What sort of transition plan would be appropriate here? Again, if this happened, we'd be changing the existing install-clang-headers target to install clang's library headers instead of its resource directory headers, and adding a new install-clang-resource-headers to install the resource directory headers, so users of the existing install-clang-headers target would have to change their builds to use install-clang-resource-headers. Some ideas I can think of:
>> 
>> 
>> 
>>  * Just note the target name change in a PSA to cfe-dev and/or the release notes and let users take it from there.
> 
> I would do both, announce it to the list and add an entry to the
> release notes.  I don't think anything else is required,
> because this target is probably not used that much anyway.

I use it, to create minimal versions of clang, e.g. just the clang executable and the required resource headers.  That is very convenient for bisecting, and way less bloated than a full installation.  That said, I don't have any strong feelings either way: a new target would be easier for me, but it is indeed less consistent.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20190222/feb1eea9/attachment.sig>