Apply Workspace

[SDGGiesbrecht]

I just configured it as close to what you have as possible.

I did not actually refresh it yet to apply the headers. If you check this branch out and double‐click the “Refresh (macOS).command” file, you’ll see it in action. Then Git will be able show you exactly the effect it had.

[NCrusher74]

thank you! I'm checking it out now!

[NCrusher74]

Okay, it does try to run, but it gets an error:

error: terminated(72): xcrun --sdk macosx --find xctest output:
    xcrun: error: unable to find utility "xctest", not a developer tool or in PATH

Anything I should worry about?

[SDGGiesbrecht]

Very strange. I’ve never seen that. (Nor do I have the slightest idea why it would be looking for xctest in the first place.) What is in the rest of the log?

[NCrusher74]

This is all I have:

nolainecrusher$ /Users/nolainecrusher/Documents/Git/SwiftTaggerID3/Refresh\ \(macOS\).command ; exit;
No cached build detected; fetching Workspace...
Cloning into '/tmp/build'...
remote: Enumerating objects: 2050, done.
remote: Counting objects: 100% (2050/2050), done.
remote: Compressing objects: 100% (1328/1328), done.
remote: Total 2050 (delta 810), reused 1415 (delta 484), pack-reused 0
Receiving objects: 100% (2050/2050), 674.16 KiB | 1.06 MiB/s, done.
Resolving deltas: 100% (810/810), done.
error: terminated(72): xcrun --sdk macosx --find xctest output:
    xcrun: error: unable to find utility "xctest", not a developer tool or in PATH

logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

It might have something to do with this prompt I get whenever I open Terminal? I never got around to updating it when I got my new computer a few months ago.

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.

[NCrusher74]

Hmm...or not. Didn't help.

[SDGGiesbrecht]

It didn’t even start. Is Xcode (which includes Swift) even installed for the command line? What do you get if you do the following in your package directory?

$ swift build

[NCrusher74]

Hm. Same error. Which is weird because I installed the command line tools and even used them a while back when I was trying to make the TagLib package

[SDGGiesbrecht]

Something probably got partially lost in an update, so that Xcode thinks it’s registered while only parts of it really are. Google seems to think this will reset Xcode for you:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

[NCrusher74]

Okay now $ swift build is working. I will try again once it's done.

[NCrusher74]

that seems to have done the trick!

[NCrusher74]

I feel sort of silly asking this but should I merge this branch after having run Workspace, or is there something else I need to do?

[SDGGiesbrecht]

You can merge.

You don’t need the test manifest file. (You never needed it on macOS. On Linux, they were only needed before Swift 5.1. Since then, there is --enable-test-discovery.)

[NCrusher74]

Ah okay. Since the manifest was automatically generated when I made the package, I assumed it had something to do with a difference in the way tests are handled for packages. Good to know, thank you!