Yep, Bazel has the same concerns with both debugging and caching cases.
I don't think there's any option to change this today, there are places in
code that assume or construct absolute paths. I have filed
https://bugs.swift.org/browse/SR-5694 to track this.
In my experience, if your output loca
And it looks like this script will stop working with 8.3 release
https://github.com/apple/swift/blob/master/utils/swift-stdlib-tool-substitute
On Mon, Feb 13, 2017 at 9:24 AM Dmitry Shevchenko wrote:
> Hello,
>
> It looks like Xcode 8.3b2 removed the swift-stdlib-tool binary. It's a
> very usefu
Hello,
It looks like Xcode 8.3b2 removed the swift-stdlib-tool binary. It's a very
useful tool that we use to copy required Swift runtime libraries in Bazel
build system.
The tool is still there in Beta 1, so I wonder it was removed by mistake in
Beta 2?
If that was intentional, can we ask to ope
The correct url is https://swift.org/blog/swift-3-1-release-process/, just
in case.
On Fri, Dec 9, 2016 at 3:55 PM Ted Kremenek via swift-lldb-dev <
swift-lldb-...@swift.org> wrote:
> The release process for Swift 3.1 has now been posted to Swift.org:
>
>https://swift.org/blog/swift-3.1-relea
