CLion 2022.2.4, Bundled cmake 3.23.3, Bundled lldb 14.0.6, Apple clang version 14.0.0 (clang-1400.0.29.102), macOS ventura 13.0.
Since I updated the system, the debugger does not hit breakpoints anymore. The breakpoint turns gray, the tooltip says "No executable code is associated with this line".
The project is a regular project with a shared library. All default (debug, no optimizations). Everything worked fine until the update. What's wrong?
After a day or two I found out that this is indeed a bug in CLion. There is an open issue for it.
Users there report that the issue is solved in the CLion Early Access Program build.
Related
I want to integrate Intel HPC Toolkit to XCode IDE but the path is not provided automatically. Which path should I choose?
I have to use XCode 11.3.1 because I cannot update the software system (It is Mojave now). I tried ~/install.sh and I got 'There is no Contents directory in XCode' error
I solved the issue. In case someone needs it: I moved XCode app from downloads folder to apps folder.
After the update debugging doesn't work in any project in CLion. By not working I imply that it ignores all the breakpoints which are not muted. Is it a common issue with macOS 10.15?
Did anyone try to add Intel Fortran Compiler to the latest XCode (version 8.3.2)? I can't find the compiler on the list. I tried to re-install the compiler entirely, linking it again to the XCode location, but nothing helped. Any idea why this happens? (I was also unable to run the simple code via terminal on Mac with the ifort command, seems like it can't link the libraries location, even though I updated the environmental variables)
The beta test compiler release notes do indicate that Xcode 8.2 is the latest supported version, as it is for the 2017u2 released compiler. Intention to offer an update 2 of the beta has been mentioned. Each minor update to Xcode apparently requires specific modifications and testing of Intel compilers.
I have installed CodeBlocks on MacBook Air. I have XCode 4.6 and XCode Command Line Tools installed. But the problem is any time I try to open an existing project CodeBlock quits unexpectedly. If I create a new project CodeBlocks crushes the same way when I open any .cpp file of the project. Anyone knows how to solve the problem?
Ok, I solved it. If anyone have the same issue try disabling Code Completion plugin in CodeBlocks (Plugins -> Manage plugins, find 'Code completion' in the list, click 'Disable').
Hope this helps.
The CodeBlocks site says "Code::Blocks for Mac is currently not as stable as are other ports, especially on Mountain Lion. In other words, we could use an extra Mac developer (or two) to work on Mac compatibility issues."
It's likely that it will just crash.
I'm sure there must be a simple explanation, I have downloaded the latest sdk and installed it using default settings in 10.7.5. I've used QT on windows before so I know how to make a project, however when I try and make a project expecting something like this to appear:
http://doc.qt.digia.com/qtcreator/images/qtcreator-new-qt-quick-project-wizard.png
But this is what I actually see:
http://trollfx.com/qt_whatisee.jpg
There are no gui project available, also none of the samples are present on the welcome page. searching for them just does nothing. I'm completely stumped, can anyone advise please?
I had the same problem.
I think what you've done is you've downloaded QtCreator as a stand alone app, and you're missing the actual Qt base files.
Uninstall QtCreator and then go to http://qt-project.org/downloads and download Qt itself, which comes with QtCreator bundled with it.
Make sure you have correctly configured the directory where Qt is installed. It needs to know where to find the qmake utility. (Specifically, go to Preferences|Build & Run|Qt Versions, click Add and locate the qmake executable).
Btw, it is assumed that you have installed XCode (at least its Unix command-line development tools.) In contrast to Windows, the Mac version does not come with a compiler. You need XCode for that.