Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to jazzy-0.1.2 with XCode 6.3 beta 1(6D520o) #170

Closed
juangamnik opened this issue Mar 1, 2015 · 13 comments · Fixed by #213
Closed

Update to jazzy-0.1.2 with XCode 6.3 beta 1(6D520o) #170

juangamnik opened this issue Mar 1, 2015 · 13 comments · Fixed by #213

Comments

@juangamnik
Copy link

I updated jazzy to v0.1.2 and my xcode-select -p set to:

/Applications/Xcode-Beta.app/Contents/Developer

When I start jazzy afterwards:

$ jazzy -c
 dyld: Library not loaded: @rpath/libswiftCore.dylib
  Referenced from: /Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/lib/jazzy/sourcekitten/sourcekitten
  Reason: image not found
/Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/lib/jazzy/sourcekitten.rb:51:in `run_sourcekitten': Running `/Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/lib/jazzy/sourcekitten/sourcekitten doc` failed:  (RuntimeError)
    from /Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/lib/jazzy/doc_builder.rb:55:in `build'
    from /Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/bin/jazzy:15:in `<top (required)>'
    from /usr/local/bin/jazzy:24:in `load'
    from /usr/local/bin/jazzy:24:in `<main>'

And a window pops up that there is a problem with the installation of sourekitten.

My hypothesis is that during installation of sourcekitten the swift code couldn't be compiled as it is not swift 1.2 compatible. But what should I do now to get it running again? change xcode-select to XCode 6.1 and reinstall the gem?

@segiddins
Copy link
Collaborator

It should be enough to have 6.1 or 6.1 installed at or symlinked to /applications/xcode.app

@juangamnik
Copy link
Author

Hmm, I have installed Xcode Version 6.1.1 (6A2006) and it is situated at /Applications/Xcode.app.

@beltex
Copy link
Contributor

beltex commented Mar 1, 2015

Hi @juangamnik! This seems to suggest that the symlink to libswiftCore.dylib is broken. Strange, as the latest release should have fixed this. Try running a ls -l (or even better tree if you have it installed; brew install tree) from inside of

/Library/Ruby/Gems/2.0.0/gems/jazzy-0.1.2/lib/jazzy/sourcekitten/SourceKittenFramework.framework/

This is how it should be

$ tree
.
├── Modules -> Versions/Current/Modules
├── Resources -> Versions/Current/Resources
├── SourceKittenFramework -> Versions/Current/SourceKittenFramework
└── Versions
    ├── A
    │   ├── Frameworks
    │   │   ├── SwiftXPC.framework
    │   │   │   ├── SwiftXPC
    │   │   │   └── Versions
    │   │   │       └── A
    │   │   │           ├── Modules
    │   │   │           │   ├── SwiftXPC.swiftmodule
    │   │   │           │   │   ├── x86_64.swiftdoc
    │   │   │           │   │   └── x86_64.swiftmodule
    │   │   │           │   └── module.modulemap
    │   │   │           ├── Resources
    │   │   │           │   └── Info.plist
    │   │   │           └── SwiftXPC
    │   │   ├── libswiftCore.dylib
    │   │   ├── libswiftCoreGraphics.dylib
    │   │   ├── libswiftDarwin.dylib
    │   │   ├── libswiftDispatch.dylib
    │   │   ├── libswiftFoundation.dylib
    │   │   ├── libswiftObjectiveC.dylib
    │   │   └── libswiftSecurity.dylib
    │   ├── Modules
    │   │   ├── SourceKittenFramework.swiftmodule
    │   │   │   ├── x86_64.swiftdoc
    │   │   │   └── x86_64.swiftmodule
    │   │   └── module.modulemap
    │   ├── Resources
    │   │   └── Info.plist
    │   └── SourceKittenFramework
    └── Current -> A

If libswiftCore.dylib is not being found then this path is invalid for some reason

../SourceKittenFramework.framework/Versions/Current/Frameworks/

@juangamnik
Copy link
Author

For me the result of tree is:

$ tree 
.
├── SourceKittenFramework
└── Versions
    └── A
        ├── Frameworks
        │   ├── SwiftXPC.framework
        │   │   ├── SwiftXPC
        │   │   └── Versions
        │   │       └── A
        │   │           ├── Modules
        │   │           │   ├── SwiftXPC.swiftmodule
        │   │           │   │   ├── x86_64.swiftdoc
        │   │           │   │   └── x86_64.swiftmodule
        │   │           │   └── module.modulemap
        │   │           ├── Resources
        │   │           │   └── Info.plist
        │   │           └── SwiftXPC
        │   ├── libswiftCore.dylib
        │   ├── libswiftCoreGraphics.dylib
        │   ├── libswiftDarwin.dylib
        │   ├── libswiftDispatch.dylib
        │   ├── libswiftFoundation.dylib
        │   ├── libswiftObjectiveC.dylib
        │   └── libswiftSecurity.dylib
        ├── Modules
        │   ├── SourceKittenFramework.swiftmodule
        │   │   ├── x86_64.swiftdoc
        │   │   └── x86_64.swiftmodule
        │   └── module.modulemap
        ├── Resources
        │   └── Info.plist
        └── SourceKittenFramework

12 directories, 19 files

@juangamnik
Copy link
Author

SourceKittenFramework is no symbolic link but concrete file:

$ file SourceKittenFramework 
SourceKittenFramework: Mach-O 64-bit dynamically linked shared library x86_64

@juangamnik
Copy link
Author

OK, I added by hand the symbolic link Current -> A and SourceKittenFramework -> Versions/Current/SourceKittenFramework. Now this issue is gone. Perhaps there is something wrong in the installation routine?

@beltex
Copy link
Contributor

beltex commented Mar 1, 2015

Yeah the symlinks are not being created for some reason, so the destination file is being put in its place. The Rakefile in lib/jazzy/SourceKitten/ handles this. I'm not sure why its failing to do so. I just tried a fresh install of jazzy, and the symlinks are created as expected. @segiddins Are you seeing the same?

@segiddins
Copy link
Collaborator

segiddins commented Mar 1, 2015

It's working for me, so I'm afraid I can't be of much help.

@beltex
Copy link
Contributor

beltex commented Mar 1, 2015

Cool, so its not just my machine then! :)

I'll check with the other thread that raised this issue previously.

@juangamnik
Copy link
Author

I tried to reinstall jazzy and it didn't help. It works for me now. But if you guys need more information for fixing the underlying problem (or just telling me how I can hold it correctly ;) ) I am eager to help. So just ask.

@beltex
Copy link
Contributor

beltex commented Mar 1, 2015

Sounds good, will do! :)

@jeeftor
Copy link

jeeftor commented Mar 21, 2015

Xcode 6.3 beta didn't work for me - but switching to 6.2 worked fine.

@juangamnik
Copy link
Author

update to jazzy v0.2.0 (XCode 6.3 installed) works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants