osx-yosemite

Unable to install Cocoapods on Yosemite DP 7

不羁的心 提交于 2019-12-01 05:27:22
问题 I am having trouble installing Cocoapods on Yosemite DP 7 installed on a separate partition. I already attempted following the instructions found on Cocoapods with Xcode 6 and 10.10 Yosemite and in the issue(https://github.com/CocoaPods/CocoaPods/issues/2219) closed due to the same solution proposed on the Stack Overflow link. I continue to get the following error: Rasmuss-MacBook-Pro:~ rasmusth$ sudo gem install cocoapods Building native extensions. This could take a while... ERROR: Error

Disable NSVisualEffectView in Source List NSTableView

一笑奈何 提交于 2019-12-01 05:01:31
问题 I have an older application that has a specific appearance based on NSCell-based NSTableView having Source List highlighting. Unfortunately, on Yosemite this adds the NSVisualEffectView vibrancy under the selected cell which breaks the appearance in an unpleasant way. I can't find a way to opt-out of this behaviour, unfortunately. Setting Regular highlighting breaks the appearance in another way (grey selection instead of blue). Any idea if there is a way to opt-out of this behaviour on 10.10

How to uninstall Qt Creator on Mac Yosemite

空扰寡人 提交于 2019-12-01 04:17:52
I have tried this but when I do, the terminal ask me for password. I don't know what this password is? I don't have any password on my mac, i don't enter any password when I login and I can't get passed the first step below. sudo QtSDK/SDKMaintenanceTool.app/Contents/MacOS/SDKMaintenanceTool I am uninstalling Qt Creator 2.8.1 on Mac OS Yosemite 10.10 I just want to install the latest 5.3.2 version and get rid of the old one. I could probably choose a new folder but I don't want to do that and it doesn't let me install over the current folder. I figured it out. Basically I was not able to

“Xcode” is damaged and can’t be opened. You should move it to the Trash

天大地大妈咪最大 提交于 2019-12-01 04:15:51
Installed XCode 6 on Mavericks . It din't run. Updated OS to Yosemite 10.10 : Now Xcode.app (installed through *.dmg) launch fails with error message “Xcode” is damaged and can’t be opened. You should move it to the Trash. Updated to XCode 6.0.1 through App Store. Still no luck. Same error message. Anyone with a fix? I experienced this error with any new added application under (all) macOS Sierra builds. The only solution that worked for me was to execute : xattr -rc /Applications/<faulty application>.app You can also use the following command to "repair" all applications : xattr -rc

Image resources (xcassets) not displayed correctly on Yosemite in application built on El Capitan using xcode6.4

*爱你&永不变心* 提交于 2019-12-01 03:46:30
When I build my application on El Capitan using Xcode6.4 (Xcode7 is no option right now), all images/icons (except the AppIcon) does not show, or looks garbled. Looking at the output from the asset compiler it looks fine, but there are two outputs I suspect could be related, but I am far from certain: 2015-10-02 12:26:53.569 ibtoold[28899:273288] NSFileCoordinator is doing nothing. 2015-10-02 12:26:54.906 ibtoold[28899:276436] CoreUI(DEBUG): CSIGenerator using 'LZFSE' Compression coreui version (362.000000) Could it be that the LZFSE compression messes up so that Yosemite is unable to

Setting environment variables in Yosemite

孤街浪徒 提交于 2019-12-01 03:27:28
问题 What is the proper way to modify environment variables like PATH in Yosemite? This is this question Setting environment variables in OS X? but specifically for yosemite since it doesn't work anymore. 回答1: Have you tried editing ~/.bash_profile ? Adding a line like this to bash_profile ought to do it: export PATH=/usr/local/bin:$PATH 回答2: What shell are you using? I'm assuming you're using the default Bash shell. There's also Csh, Ksh, and Zsh. The Terminal.app on Mac OS X by default starts a

“Xcode” is damaged and can’t be opened. You should move it to the Trash

风流意气都作罢 提交于 2019-12-01 01:11:29
问题 Installed XCode 6 on Mavericks . It din't run. Updated OS to Yosemite 10.10 : Now Xcode.app (installed through *.dmg) launch fails with error message “Xcode” is damaged and can’t be opened. You should move it to the Trash. Updated to XCode 6.0.1 through App Store. Still no luck. Same error message. Anyone with a fix? 回答1: I experienced this error with any new added application under (all) macOS Sierra builds. The only solution that worked for me was to execute : xattr -rc /Applications/

Swift Bindings won't work Xcode 6 Beta 5

拥有回忆 提交于 2019-11-30 18:41:55
I'm doing a simple test program using bindings in Swift on OSX. Having an NSTableView, NSArrayController and a model class I try to hook them up together, but without success! The build compiles but gives instantly this error: Thread 1: EXC_BAD_ACCESS(code=1, address = 0x0) Code looks like this: model class: import Foundation class Name { var firstName = "Brook" var lastName = "Brooklyn" } view controller: import Cocoa class ViewController: NSViewController { dynamic var names = [Name]() // serves as the content for Array-Controller override func viewDidLoad() { super.viewDidLoad() // populate

iOS ipa codesign on XCode 6.1 & Yosemite

点点圈 提交于 2019-11-30 17:30:39
I was used to sign my app with the following command codesign --resource-rules=ResourceRules.plist -f -s "SIGNER_NAME" MYAPP.app After installing Yosemite and XCode 6.1 it gives the following warning: Warning: --resource-rules has been deprecated in Mac OS X >= 10.10! So I tried to remove the "--resource-rules" but now it gives the following (blocking) error: invalid resource specification rule(s) Is there any right way to codesign ? g_blott Over on this post They answer your question. That post is more targeted towards using a build server (Jenkins CLI) but the answer is the same for you (and

Is it ok to install both Python 2.7 and 3.5?

好久不见. 提交于 2019-11-30 17:21:04
Supposedly Python 2.7 is included native to OSX 10.8 and above (if I remember correctly), but I recently installed Python 3.5 to use for projects while I work through UDacity. Lo and behold, the UDacity courses seem to use 2.7 - wups! So instead of trying to uninstall 3.5 (this procedure seemed to scary for neophytes such as myself), I simply installed 2.7 in addition to the recently installed 3.5 and just run the 2.7 IDLE and Shell. Is this ok, or will I run into problems down the road? I have installed two versions, 2.7, 3.4 and I do not have any problem by now. 3.4 I am using for my work