# Command line applications crashes with Xcode 10.2 **URL:** \ **Category:** Using Swift\ **Created:** [March 27, 2019, 9:07am UTC](https://forums.swift.org/t/command-line-applications-crashes-with-xcode-10-2/22192 "2019-03-27T09:07:26Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![jrose](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jrose/32/408_2.png) [@jrose](https://forums.swift.org/u/jrose)\ **Post date:** [March 27, 2019, 4:04pm UTC](https://forums.swift.org/t/command-line-applications-crashes-with-xcode-10-2/22192/7 "2019-03-27T16:04:14Z")
Previous versions of Swift allowed static linking of the standard library and runtime on macOS, but that's not going to work anymore because parts of the OS also link against the standard library and runtime, and the two wouldn't be able to interoperate. (We had to jump through hoops not to break Swift 4-and-below apps, but we know that those aren't trying to talk to any of the Swift parts of the system, because there _were_ no Swift parts of the system when those were deployed.) We're in an inconvenient spot now, but in the long run this won't be a problem. > [@Jon\_Shier](#): > > Won't those be stripped if shipped through the App Store on systems with the system libs? Yes, which is why you also need to have a Runpath Search Path for /usr/lib/swift/. --- _[View the full topic](https://forums.swift.org/t/command-line-applications-crashes-with-xcode-10-2/22192)._