-
Notifications
You must be signed in to change notification settings - Fork 62
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
Precompiled version? #1
Comments
Hey, no problem, and if at any point you think you might be able to contribute, feel free to! About the compiled version; probably yes. To be honest, I thought I had posted it already. |
I second that! A precompiled version would be very handy. |
Agree. I see «To install, double click on the .prefpane, and you will be prompted to install it.» in README.MD, but there is no any .prefpane files :) It should be useful. And big thanks for your work. |
Not so easy to compile for everyone, i'll be waiting for compiled version too, thanks. |
@Lord-Kamina I get the following error:
|
Same here. |
Yeah it seems Xcode fucked something up; let me see what’s up and I’ll
upload again.
|
Am fixing the issue now, problem is for some reason not all @objc inferences registered warnings so I ended up having to look some up by hand. |
Should be fixed now. |
I think that checksum is wrong. I'll reupload the archive. md5 should be c7a2391390ac3ef3d106a83ecb3b9e2d EDIT: Try now. |
I re-downloaded, and I do have the |
Try deleting the previous version entirely and copying it over again? |
Yes, I've done that. I'm on 10.13 (17A365) |
It might be a High Sierra issue? Try this... Open a Terminal and run
Replace the location of the prefpane as appropriate. That should give a somewhat more verbose idea of what the issue actually is. |
Here's what I get :
|
I've got no idea what the issue is, but it's most likely to do with Swift 4. Hope SO or some other place can shed some light. |
Dear @Lord-Kamina, I just want to say it works well for me on 10.11.6. Thanks. |
I got the same error as luckman212 on 10.13 |
I
I had already confirmed the bug by asking my brother to try it. I don't really know yet what is causing it, though, so please be patient.
…On October 1, 2017 at 11:31:16, Gediminas ***@***.******@***.***)) wrote:
I got the same error as luckman212 on 10.13
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub(#1 (comment)), or mute the thread(https://github.com/notifications/unsubscribe-auth/AGJfLJQaUR2vqAxR4OuuNDcATatr2kGJks5sn6I0gaJpZM4PKJH6).
|
I think it's a bug to do with Runpath search paths that apparently behave differently on 10.13, but haven't been able to figure it out yet. |
@xayoung I accidentally deleted your comment because am sleepy and from mu cell. Could you try this version? https://www.dropbox.com/s/q8bweehizosklv3/SwiftDefaultApps-1.1.0.7z?dl=0 Put it in the appropriate folder and try running it with the following
And post the output of that please? |
I download the file from dropbox, and run as above. The error is below: |
I haven't been able to solve this. I think it's a bug in Swift.
…On November 4, 2017 at 08:44:03, gebing ***@***.***) wrote:
2017-11-04 19:43:24.995 System Preferences[49977:1930442] Error loading
/var/root/Library/PreferencePanes/SwiftDefaultApps.prefPane/Contents/MacOS/SwiftDefaultApps:
dlopen(/var/root/Library/PreferencePanes/SwiftDefaultApps.prefPane/Contents/MacOS/SwiftDefaultApps,
265): can't resolve symbol *OBJC_CLASS*$_NSError in
/private/var/root/Library/PreferencePanes/SwiftDefaultApps.prefPane/Contents/MacOS/../Frameworks/libswiftCore.dylib
because dependent dylib #1
<#1> could not be
loaded in
/private/var/root/Library/PreferencePanes/SwiftDefaultApps.prefPane/Contents/MacOS/../Frameworks/libswiftCore.dylib
2017-11-04 19:43:24.995 System Preferences[49977:1930442]
[NSPrefPaneBundle instantiatePrefPaneObject]
(/var/root/Library/PreferencePanes/SwiftDefaultApps.prefPane):
principalClass is nil.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGJfLBQWEp9eNJSVpk0AAikmMRjBsqjqks5szE4DgaJpZM4PKJH6>
.
|
I reproduced it myself on my brother’s (running HS) laptop. As I said earlier, I believe this might be a bug in Swift. While it’s a known fact Swift is not yet ABI compatible and one cannot load binaries compiled against one version alongside binaries compiled against another, it strikes me as definitely odd that it would work on Sierra and not on High Sierra. Especially considering Sierra has Swift 3 an High Sierra Swift 4 (which is what the prefpane was compiled and linked against)
…--
Gregorio Litenstein Goldzweig
Médico Cirujano
Fono: +56 9 96343643
E-Mail: [email protected]
On November 7, 2017 at 11:32:48, Quentin Dreyer ([email protected]) wrote:
https://gist.github.com/qkdreyer/dc1561b39b9e87ed1557c565c87ac8d4
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
FWIW, I'm not getting any errors from libswiftCore.dylib SwiftDefaultApps 1.1.0 on macOS High Sierra 10.13.4 (17E199). https://gist.github.com/qkdreyer/dc1561b39b9e87ed1557c565c87ac8d4/revisions Now, I'd contribute to https://github.com/caskroom/homebrew-cask/ by adding a cask, but only release having .dmg/.zip/.tgz/.tbz2 extension are supported. Could you publish a new release with one of these extension instead of .7z @Lord-Kamina ? |
I'm visiting the USA so not at the moment. I'll pick my new laptop in a week. Then I can test properly in 10.13 and also swift 4.1. Will get back to you. |
@qkdreyer I just built and tested it with the latest Xcode and Swift 4.1 on 10.13.4 and it appears to be running fine indeed. I'd completely forgotten about the 7z issue though, sure, I'll do one of those. |
I had the same problem on High Sierra 10.13.3. @Lord-Kamina I think you can close this issue |
You can install the prefpane with |
|
While I think it's cool that the prefpane was added to Homebrew (and thus reached more people) I'm loath to do this because I really dislike Homebrew and would rather not encourage it. For the sake of saving a couple keystrokes for novice users, Homebrew introduces a sizable security vulnerability into macOS by changing the permissions of |
@Lord-Kamina I don't think that's a concern anymore. Homebrew now uses |
First, thank you for writing this!
Any chance you'll release a precompiled prefPane on GitHub? It was pretty easy to build with Xcode, but it would still be convenient to have.
The text was updated successfully, but these errors were encountered: