The other thing needed is to put it somewhere Xcode will find it, either in the system Library or the user local Library Toolchains directory.
I personally do this by having a symlink from: ~/Library/Developer/Toolchains/swift-dev.xctoolchain to a version I build up with Swift (with an Info.plist) inside of the Swift build directory. This allows me to do TOOLCHAINS=swift-dev swift ... for many of my workflows. - Daniel > On May 4, 2016, at 10:22 AM, Jordan Rose via swift-dev <swift-dev@swift.org> > wrote: > > You don't actually need to sign the toolchain; it just needs an Info.plist. > Dmitri, Mishal, is there any reason the build-toolchain script doesn't > provide one? > > Jordan > > >> On May 3, 2016, at 23:43, Rob Allen via swift-dev <swift-dev@swift.org> >> wrote: >> >> Hi, >> >> I've used swift/utils/build-toolchain to create a toolchain from the tip of >> master. To use this in Xcode, I think it needs to be signed. How do I do >> this? >> >> >> Regards, >> >> Rob... >> _______________________________________________ >> 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 _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev