[swift-users] Disable "indexing while building" in Xcode9 (unknown argument: `-index-store-path`)

Tue Jul 4 22:21:11 CDT 2017

I think the indexing while building is really part of Xcode and not Swift since it also works on C, C++, Obj-C and Obj-C++.  It’s not just for Swift.
Jonathan

> On Jul 4, 2017, at 11:18 PM, Jon Shier <jon at jonshier.com> wrote:
> 
> 	The feature this thread is about, indexing while building. I’m of the opinion that, if a feature needs to be integrated with the Swift compiler, as this one was, development of that integration should be done in the open. Perhaps I misunderstand how this feature is separated between the compiler and higher level tools, but avoiding a month long mismatch between the open source and Apple versions, one which prevents open source snapshots from working in Xcode at all, is a good thing, no?
> 
> 
> 
> Jon
> 
>> On Jul 4, 2017, at 11:14 PM, Jonathan Prescott <jprescott12 at icloud.com <mailto:jprescott12 at icloud.com>> wrote:
>> 
>> I’m curious what Swift features you think Apple is developing internally that is not being done concurrently as part of, or totally within, the open-source project.  To me, everything that is the compiler(s), debugger, standard librarIes, package manager are all being constructed completely within the open-source community (both LLVM/CLang and Swift).  All of the Xcode pieces you explicitly mentioned (the source code editor, the build system, for example) are all part of the Xcode application, and should be developed by Apple as part of their product offering to whatever level of privacy they desire.  And, the iPad Playgrounds Application is Apple-proprietary as well.
>> 
>> What components/Swift features are you concerned about?
>> 
>> Just asking.
>> 
>> Jonathan
>> 
>>> On Jul 4, 2017, at 9:20 PM, Jon Shier via swift-users <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>>> 
>>> 	Xcode 9 fixes my biggest complaint about Xcode, which was the text editor. The new one, based off the one used in the Playgrounds iPad app, is far better in pretty much every way than the old one. It’s still missing features (which should be added by release) but I use it as much as I can. It still suffers from some of the same issues as the old editor, namely that its functionality breaks almost completely when SourceKit crashes, which is really annoying for stuff like syntax highlighting and auto indentation, since it seems like that stuff shouldn’t break when that happens. But it recovers a bit better now from those situations. The new build system is also really nice, though largely invisible.
>>> 	I do find it concerning that Apple is developing Swift features internally, which is rather antithetical to open source development and leads to painful transition periods like this where Apple’s version and the open source version are out of sync. It really doesn’t seem necessary for these features to be developed privately. I would hope the Swift project takes a more WebKit-like approach to these features, where all features are developed in the open source branch, with only the SPI integration private to Apple. Features like the content filters shipped last year were fully visible in the open source tree long before WWDC. It would be better for Swift to develop all of these features in the open.
>>> 
>>> 
>>> 
>>> Jon
>>> 
>>>> On Jul 4, 2017, at 9:05 PM, David Baraff via swift-users <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>>>> 
>>>> How is xcode9 beta going in general?  I would dearly love to start using the new Codable stuff, and I don’t have to really worry about swift 3 compatability — it’s just a question of the xcode 9 beta being safe enough to get work done.
>>>> 
>>>> (The fact that “yank” was broken makes it a non-starter for me but i’m kind of hoping it gets fixed soon.)
>>>> 
>>>> 
>>>>> On Jul 4, 2017, at 6:02 PM, Anders Hasselqvist via swift-users <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> I've been trying to use the swift4 snapshot toolchains with Xcode9 beta with little success.
>>>>> 
>>>>> When building I get the error:
>>>>> "
>>>>> <unknown>:0: error: unknown argument: '-index-store-path'
>>>>> Command /Library/Developer/Toolchains/swift-4.0-DEVELOPMENT-SNAPSHOT-2017-06-29-a.xctoolchain/usr/bin/swiftc failed with exit code 1
>>>>> "
>>>>> 
>>>>> I believe that this because of missing "indexing while building" support in the open source swift in the currently available snapshots. (The feature was merged just a few days ago: https://github.com/apple/swift/pull/10726 <https://github.com/apple/swift/pull/10726>)
>>>>> 
>>>>> Is there a way to disable "indexing while building" in Xcode9?
>>>>> 
>>>>> Thanks,
>>>>> Anders
>>>>> 
>>>>> _______________________________________________
>>>>> swift-users mailing list
>>>>> swift-users at swift.org <mailto:swift-users at swift.org>
>>>>> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>
>>>> 
>>>> _______________________________________________
>>>> swift-users mailing list
>>>> swift-users at swift.org <mailto:swift-users at swift.org>
>>>> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>
>>> 
>>> _______________________________________________
>>> swift-users mailing list
>>> swift-users at swift.org <mailto:swift-users at swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20170704/db3dec3e/attachment.html>