site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt1383820pop.onmicrosoft.com; s=selector1-sandoeacoustics-co-uk01e; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=E6rnQ7RuX4qM+SkCFoXvYkgteBa1ByT9J25GKw7PK6Y=; b=OWA92pz/CA4pIOFrhnG2ddn7h2Yb65l6m9MXUaIqGN25EF1ujQdLx9Jd7ELo50KbBrGbM4Pd3Xo0K/2AMZes0Y2BXpz52hpox+6HTTh7AOtgVAoXMUnDms3O628POX3NgN8VGZrpGvlg7Qd+UODFW19bC1xTde9m4ea8AXCgG7k= Spamdiagnosticmetadata: NSPM Spamdiagnosticoutput: 1:99 Thread-index: AQHUkG+38LV1P42G5UWGrXBnH+QV9aV5OMMAgAAD+YCAACQBgIAABHAA Thread-topic: Dev Tools 9 missing Folks,

On 11 Dec 2018, at 11:01, Michael Crawford <mike@soggywizards.com> wrote:

I wasn't griping about the LLVM license.

I wasn't even griping about Apple.

It was not my intention to start *any form* of discussion on licensing (IANAL). The “status quo” was that Apple has previously posted the TAPI and clang/llvm components for the xcode toolchain. For those of us who build toolchains, and have an interest in ensuring ABI compatibility between compilers, it would be a tremendous help if these components would continue to be posted It would be great to know the intentions, nothing more was meant by my post than that. (as an aside) It is also the case that tapi itself is a worthy consideration for inclusion into the LLVM project (but that is yet another discussion for a different list) thanks Iain _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app... This email sent to site_archiver@lists.apple.com