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


(Anders Hasselqvist) #1

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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders


(David Baraff) #2

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@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users


(Jon Shier) #3

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@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@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users


(Jonathan Prescott) #4

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@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users


(Jon Shier) #5

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@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users


(Jonathan Prescott) #6

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@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@icloud.com <mailto:jprescott12@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users


(Jon Shier) #7

It had to be merged from Apple’s upstream changes, as pointed out at the start of this thread, so the feature requires compiler integration. It’s likely the same work was done in clang/llvm for the C-based language side of things. Even if it’s an Apple-only feature (as this index format seems Apple specific, according to the comments in the merged PR), once it touches the compiler, development should be done in the open and not as upstream dumps, IMO. Otherwise things can get out of sync pretty badly.

Jon

···

On Jul 4, 2017, at 11:21 PM, Jonathan Prescott <jprescott12@icloud.com> wrote:

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@jonshier.com <mailto:jon@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@icloud.com <mailto:jprescott12@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users


(Alex Blewitt) #8

A workaround is to add SWIFT_INDEX_STORE_ENABLE=NO as a build time setting in Xcode, which prevents this argument being added to the call to swiftc.

···

On 5 Jul 2017, at 02:02, Anders Hasselqvist via swift-users <swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users


(Jens Persson) #9

I'm using Xcode 9 beta 2 (on Sierra 10.12.5) and my top 3 annoyances are:

1. Having to manually scroll the text editor sideways to follow the
caret/cursor as it moves out of view (!) while editing a line that is wider
than the text editor.

2. Non-working "File -> Add Files" (Options: Copy items if needed
unchecked) displaying cryptic error dialog message:
"An assistant session is already running on this window"
Have to use drag and drop as a workaround.

3. Jump to definition of std lib types / funcs more buggy than in 8.3.3
(sometimes not able to locate the definition, no visible cursor when in the
jumped-to editor).

I was surprised 1 hadn't been fixed in the second beta. Is everyone
assuming that it must have been reported thousands of times already, or am
I the only one experiencing it?

/Jens

···

On Wed, Jul 5, 2017 at 10:53 AM, Alex Blewitt via swift-users < swift-users@swift.org> wrote:

A workaround is to add SWIFT_INDEX_STORE_ENABLE=NO as a build time
setting in Xcode, which prevents this argument being added to the call to
swiftc.

On 5 Jul 2017, at 02:02, Anders Hasselqvist via swift-users < > swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users


(Alex Blewitt) #10

Did you file radars for the below? If others have already reported it, then yours will count as a dupe towards it, and the more dupes that a specific radar has the higher visibility it has.

Alex

···

On 5 Jul 2017, at 10:37, Jens Persson <jens@bitcycle.com> wrote:

I'm using Xcode 9 beta 2 (on Sierra 10.12.5) and my top 3 annoyances are:

1. Having to manually scroll the text editor sideways to follow the caret/cursor as it moves out of view (!) while editing a line that is wider than the text editor.

2. Non-working "File -> Add Files" (Options: Copy items if needed unchecked) displaying cryptic error dialog message:
"An assistant session is already running on this window"
Have to use drag and drop as a workaround.

3. Jump to definition of std lib types / funcs more buggy than in 8.3.3 (sometimes not able to locate the definition, no visible cursor when in the jumped-to editor).

I was surprised 1 hadn't been fixed in the second beta. Is everyone assuming that it must have been reported thousands of times already, or am I the only one experiencing it?

/Jens

On Wed, Jul 5, 2017 at 10:53 AM, Alex Blewitt via swift-users <swift-users@swift.org <mailto:swift-users@swift.org>> wrote:
A workaround is to add SWIFT_INDEX_STORE_ENABLE=NO as a build time setting in Xcode, which prevents this argument being added to the call to swiftc.

<PastedGraphic-1.png>

On 5 Jul 2017, at 02:02, Anders Hasselqvist via swift-users <swift-users@swift.org <mailto:swift-users@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)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org <mailto:swift-users@swift.org>
https://lists.swift.org/mailman/listinfo/swift-users


(Jens Persson) #11

I did not file radars for them, as they seem so flagrant.

I have to draw the line somewhere or my entire working days would be spent
filing radars (including isolating the issues and coming up with good
descriptions of them in english, collecting crash logs etc, etc).

Reporting less obvious Swift bugs that I really want to see fixed to Jira
is already taking more of my time than I'd like.

/Jens

···

On Wed, Jul 5, 2017 at 11:44 AM, Alex Blewitt <alblue@apple.com> wrote:

Did you file radars for the below? If others have already reported it,
then yours will count as a dupe towards it, and the more dupes that a
specific radar has the higher visibility it has.

Alex

On 5 Jul 2017, at 10:37, Jens Persson <jens@bitcycle.com> wrote:

I'm using Xcode 9 beta 2 (on Sierra 10.12.5) and my top 3 annoyances are:

1. Having to manually scroll the text editor sideways to follow the
caret/cursor as it moves out of view (!) while editing a line that is wider
than the text editor.

2. Non-working "File -> Add Files" (Options: Copy items if needed
unchecked) displaying cryptic error dialog message:
"An assistant session is already running on this window"
Have to use drag and drop as a workaround.

3. Jump to definition of std lib types / funcs more buggy than in 8.3.3
(sometimes not able to locate the definition, no visible cursor when in the
jumped-to editor).

I was surprised 1 hadn't been fixed in the second beta. Is everyone
assuming that it must have been reported thousands of times already, or am
I the only one experiencing it?

/Jens

On Wed, Jul 5, 2017 at 10:53 AM, Alex Blewitt via swift-users < > swift-users@swift.org> wrote:

A workaround is to add SWIFT_INDEX_STORE_ENABLE=NO as a build time
setting in Xcode, which prevents this argument being added to the call to
swiftc.

<PastedGraphic-1.png>

On 5 Jul 2017, at 02:02, Anders Hasselqvist via swift-users < >> swift-users@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
)

Is there a way to disable "indexing while building" in Xcode9?

Thanks,
Anders

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users

_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users