Re: [swift-users] SwiftProtobuf unable to link on Ubuntu

> On 14 Oct 2017, at 21:41, Geordie J via swift-users > wrote: > >> swift build -Xswiftc -I/home/ed/swift-protobuf/.build/release -Xlinker >> -L/home/ed/swift-protobuf/.build/release > > Have you considered using Swift Package Manager to add protobuf as a project >

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Thanks for the analysis. Can you create a bug at https://bugs.swift.org and attach the reproducing test case? That way it can be routed to the appropriate people, in case they're not on this mailing list. Alex > On 13 Oct 2017, at 22:09, Edward Connell via swift-users

Re: [swift-users] SwiftProtobuf unable to link on Ubuntu

Hi Alex, Yes of course using the Swift PM is what I needed to do. What was I thinking! ;p It worked, however SwiftProtobuf 1.0.0 does not build cleanly with Swift 4.0 due to the rework of the Strings API. I hope someone will clean that up soon. I appreciate your feedback and time, Ed On Mon,

Re: [swift-users] Why does the withUnsafeMutableBufferPointer closure take an inout parameter?

> On Oct 13, 2017, at 7:40 PM, Andrew Trick via swift-users > wrote: > > > >> On Oct 12, 2017, at 3:52 AM, Geordie Jay via swift-users >> > wrote: >> >> >> Guillaume Lessard via swift-users

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

While creating a bug report for this problem I placed my simple repro case in a separate project with default build settings and I found that it no longer crashes LLDB. My main project links to several system C libraries, because I am using libpng, Cuda, etc... In order for LLDB to function with

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

> On 16 Oct 2017, at 18:52, Edward Connell wrote: > > While creating a bug report for this problem I placed my simple repro case in > a separate project with default build settings and I found that it no longer > crashes LLDB. > > My main project links to several system C

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Specifying the clang import location is what is triggering the LLDBFrontend crash. I think you are saying that I should not need to specify the clang include import location to the compiler. I've attached the unmodified SwiftProtobuf example program found in the docs at

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Please record this in a bug at bugs.swift.org so that it doesn’t get lost, if you haven’t already. Thanks! Alex Sent from my iPhone  > On 16 Oct 2017, at 19:56, Edward Connell wrote: > > Specifying the clang import location is what is triggering the LLDBFrontend >