macos-catalina

Xcode 11.1: iostream' file not found

人盡茶涼 提交于 2019-12-06 06:02:05
I just updated my MacBook Pro to macOS Catalina 10.15 , and tried to compile and run a C++ command line program , but I had a problem which didn’t exist on previous versions; This is simply the code: #include <iostream> using namespace std; int main() { cout << "Hello, World!\n"; return 0; } The code compiles and outputs the expected, but still the Xcode says: fatal error: 'iostream' file not found I tried changing the Build Settings/C++ Standard Library to libstdc++ , but a warning says: warning: include path for stdlibc++ headers not found; pass '-stdlib=libc++' on the command line to use

Can't update Xcode 11 [closed]

家住魔仙堡 提交于 2019-12-04 22:12:09
Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last month . Trying to update from Xcode 11 GM to 11.1 always fail. I tried moving /Applications/Xcode.app first... nothing works This is my commerce log: 2019-10-08 12:29:08+01 leviathan installd[556]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=501 "The package is attempting to install content to the system volume." UserInfo={NSLocalizedDescription=The package is attempting to install content to the

Flutter Issues with MacOS 10.15 Catalina

淺唱寂寞╮ 提交于 2019-12-04 14:02:59
问题 After updating to MacOS 10.15 Catalina , there are problems with Flutter . Specifically, Flutter doctor complaints about the following: Downloaded executables cannot execute on host. CocoaPods not installed. It is important to explain that before updating, when my computer was running Mojave 10.14 , these issues with Flutter did not exist , thus flutter doctor -v reported no issues whatsoever. Regarding the first issue: Downloaded executables cannot execute on host. Flutter doctor offers this

Is there a way to install Valgrind on Catalina?

做~自己de王妃 提交于 2019-12-04 11:28:42
问题 Is there a way to install Valgrind on Catalina and have it run properly? If so, I would very much appreciate a step-by-step process. I tried installing Valgrind with https://github.com/sowson/valgrind but when I tested out helloWorld.cpp on the terminal, the console returned errors I should not have gotten. I'm not sure if I committed an error on my part in the installation process of this version of Valgrind or if Valgrind itself is simply incompatible with Catalina OS. I have also tried

Flutter Issues with MacOS 10.15 Catalina

社会主义新天地 提交于 2019-12-03 16:17:53
After updating to MacOS 10.15 Catalina , there are problems with Flutter . Specifically, Flutter doctor complaints about the following: Downloaded executables cannot execute on host. CocoaPods not installed. It is important to explain that before updating, when my computer was running Mojave 10.14 , these issues with Flutter did not exist , thus flutter doctor -v reported no issues whatsoever. Regarding the first issue: Downloaded executables cannot execute on host. Flutter doctor offers this link: https://github.com/flutter/flutter/issues/6207 Nevertheless, the linked article refers to Linux

macOS Catalina 10.15(beta) - Why is `.~bash_profile` not sourced by my shell?

一世执手 提交于 2019-12-03 12:11:44
I want to set the environment variable I added below the line to ~/.bash_profile and ~/.profile but it didn't work. export JBOSS_HOME=/Users/{USERNAME}/Desktop/jboss7 Afterward, exit the terminal and open it again when executing echo $JBOSS_HOME I get nothing. Apple has changed the default shell to zsh. Therefore you have to rename your configuration files. .bashrc is now .zshrc and .bash_profile is now .zprofile . I created a new file called /usr/local/bin/mybash which contains a wrapper script: /usr/local/bin/bash --init-file $HOME/.bashrc I installed this local/bin/bash from HomeBrew . Full

Xcode fails to Build on real iOS device running iOS 13

天大地大妈咪最大 提交于 2019-12-03 09:28:06
问题 I'm currently updated my iPhone XS Max to iOS 13.0.17A5492t Beta version. My mac running on Mac OS Catalina and Xcode is on latest stable version not beta >> Version 10.2.1 (10E1001) . When i try to build my apps on my real device i get this compile error: This iPhone XS Max is running iOS 13.0 (17A5492t), which may not be supported by this version of Xcode. What i've done Download iOS 13.0 Developer Disk Image from repo. Pasted in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS

Python crashing on MacOS 10.15 Beta (19A582a) with “/usr/lib/libcrypto.dylib”

笑着哭i 提交于 2019-12-03 06:28:58
问题 I ran my Django project with new macOS Catalina and was running fine. I installed oh_my_zsh then I tried to run the same project it is crashing with the following errors. I uninstalled oh_my_zsh and tried again but it did not worked. Path: /usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: 3.7.4 (3.7.4) Code Type: X86-64 (Native) Parent Process: Python [7526] Responsible: Terminal [7510] User ID: 501

Xcode fails to Build on real iOS device running iOS 13

牧云@^-^@ 提交于 2019-12-03 02:59:24
I'm currently updated my iPhone XS Max to iOS 13.0.17A5492t Beta version. My mac running on Mac OS Catalina and Xcode is on latest stable version not beta >> Version 10.2.1 (10E1001) . When i try to build my apps on my real device i get this compile error: This iPhone XS Max is running iOS 13.0 (17A5492t), which may not be supported by this version of Xcode. What i've done Download iOS 13.0 Developer Disk Image from repo. Pasted in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport Restart Xcode but none of above worked. your step by step manual you performed

applicationShouldTerminate not called in AppDelegate and NSApplicationWillTerminateNotification not being sent

旧巷老猫 提交于 2019-12-02 03:18:40
问题 I'm on XCode 11.1 on latest Catalina and none of my app's quit events are being called. applicationShouldTerminate in the AppDelegate nor do I get NSApplicationWillTerminateNotification if I observe it from anywhere. This is from the default quit behavior (Using the menu quit command, Command-Q, or closing the window with applicationShouldTerminateAfterLastWindowClosed returning YES) from the XCode app template using the default storyboard. This happens with a brand new Xcode project template