Excellent! That did the trick… Just out of curiosity, where is that documented? The trunk llvm plist is an old Info.plist with an odd (dated) structure, I did have to “modernize it along the lines of the default Xcode default one. Just wondering if there are any other fields I need to set. Is there a unique swift toolchain packaging “project” I can study to figure all this out on my own?
Thanks much in advance, Regards, Patrice > On Aug 19, 2016, at 5:08 PM, Daniel Dunbar <daniel_dun...@apple.com> wrote: > > Is CompatibilityVersion set in the LLVM toolchains? IIRC, Xcode 8 requires it > to be 2. > > - Daniel > >> On Aug 19, 2016, at 1:12 PM, Patrice Kouame via swift-dev >> <swift-dev@swift.org> wrote: >> >> Hi all - Xcode doesn't recognize my llvm toolchain even though it was built >> right out of llvm trunk with llvm toolchain enabled. However, Swift >> toolchains are imported with ease into Xcode. Just by dropping into >> toolchains. I'd like to find out more about how swift manages to package >> their toolchains so that Xcode doesn't complain about incompatibility. >> What's the secret sauce? Can any one point me in the right direction? Is it >> signing related? I'm on a bleeding edge environment with Sierra public beta >> and Xcode 8 beta. >> Currently I just change my path to "enable" my preferred clang toolchain, >> but would like to avoid that in the future by switching with xcode-select. >> Any help is greatly appreciated... >> >> Patrice >> >> _______________________________________________ >> swift-dev mailing list >> swift-dev@swift.org >> https://lists.swift.org/mailman/listinfo/swift-dev > _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
