Before I updated both QT and Xcode on my mac, my computer just stopped opening up the terminal when I went to run my code. It had worked for months and is still enabled as my default on QT. I Tried uninstalling and reinstalling both QT and Xcode, but my terminal still will not open when I run the code. When I disable terminal as my default, I can see my output at the bottom of my screen in QT, but I would like it to open in terminal. Any suggestions?
Someone on https://forum.qt.io found the solution, thank's so much to him !
A .dmg archive with a corrected QtCreator version 7.0.1 from the snapshot downloads is available here: https://download.qt.io/snapshots/qtcreator_qt5/7.0/7.0.1/134/
After installation, the terminal opens correctly
Related
I am trying to get clang_complete to run on macOS preinstalled vim.
This is what I have done.
Installed PlugInstall
Tested it with other Plugins if it works and it worked just fine with COC(another autocompletion tool but without C support )
placed this bit of code into my .vimrc file:
call plug#begin('~/.vim/plugged')
"Plug 'neoclide/coc.nvim', {'branch': 'release'} //This worked fine
Plug 'rip-rip/clang_complete' //This installed just fine but doesnt work
call plug#end()
let g:clang_library_path='/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib' //Path to libclang
Now I opened vim and ran :PlugInstall, which worked just fine
Opened a .c file and the file doesnt even open. Just a blank grey screen from the theme I am using and I have to force quit my terminal.
Any suggestions what I am doing wrong ?
Try :CocInstall coc-clangd, this will use clangd to do completion. You need to install clangd first: https://clangd.llvm.org/installation.html
I've looked for an answer during a few days and I haven't found anything similar anywhere;
I downloaded Qt from the official website, installed it and apparently compiling is fine. But whenever I try to execute (Ctrl+R) any app, even the basic one which only displays a window or widget, QtCreator itself crashes. No error message, nothing, just crashing.
I've tried to redownload and reinstall it a few times with different settings, but nothing will do.
I'm running QtCreator on Windows 7 64 bits. I'll try on my laptop which is also running windows and will update if I find anything.
Any help would be appreciated, I need to start a project as soon as possible. I'm relatively new to QT and if you need info on anything just ask me. Thanks :)
Use dependency walker, http://www.dependencywalker.com/
and post any missing dependencies. It is possible some install targets or options are missing from when you installed QtCreator, which can be resolved with the maintenance tool in the same directory you installed Qt.
Also, are you using the Visual Studio compiler(must have Visual Studio installed separately, and mark the option during install), or the Ming compiler(2 options checked during install or maintenance)?
Check if your antivirus is locking it, I had a similar issue time ago and it was due to antivirus (Avast specifically). Disable antivirus' realtime shields and try to execute a basic app.
It is necessary to use QtCreator? I use QtDesigner snd VS2013 and things go very well. :)
check this thread Qt Creator Plain C++ Project won't run/debug... and this C++ - QtCreator doesn't show any output
I just installed Qt creator on OSX and after compiling my first program (nothing fancy, just "hello world"), I tried to run it. It opened a terminal without my hello world, just saying "press enter to close".
I read similar topics of Stackoverflow on this matter like this one :
Console input with Qt Creator
I did the two steps ("Run in Terminal" which was already checked by default and set the path to xterm "/usr/x11/bin/xterm -e", I checked that I had indeed xterm at this path after installing x11). But unfortunately, when I run my program, in the app output of Qt creator, I just have the message :
Starting
/Users/Michael/build-First-Desktop_Qt_5_5_1_clang_64bit-Debug/First...
and then nothing else happens, no terminal. Has someone already faced this problem?
Thanks in advance
Recently I have re-installed QT (5.5.1 MSVC 2013, 32 bit, rev. b52c2f91f5) on my PC and installed the debugging tools of Microsoft.
QT (QT Creator) can auto-detect these just fine.
When trying to start the debugger with either the default shortcut F5 or clicking it manually, it throws an error that the debugger could not be run. (Compiling works fine, debugging not at all)
No debugger-engine of type "No engine" could be created.
(Running Windows 8.1 with VS2013/VS2015 installed - QT working with VS2013 32&64 bit).
On my work PC I did the same process a few weeks ago and had no problems at all.
What could cause this problem ? Yet I have only found questions with the same problem related to other compilers.
It may point to a missing component in your installation process or an actual defect in Qt:
Option #1
Install a debugger.
If you are installing 5.5.1 for Visual Studio 2013 64 or 32bit, 2012
32bit, 201032bit. Then install windows Debuggers.
Qt will detect automatically the compiler and Debugger.
To set manually Tools->options->build&run->kits->set one of auto detected , then
you can see all.
Source: https://forum.qt.io/topic/59974/unknown-debugger-type-no-engine/11
Option #2
Unable to create a debugger engine of the type "No engine"
in the past pointed to a bug in the Qt Creator, if you'll update it may be fixed.
I'm also aware that alternatively, it may be solved by updating to Python 2.7.1.
Close Qt Creator.
In the folder where your .pro file resides, there will be some .pro.user and .pro.user.x files. Delete them all. Keep only your .pro file.
Start Qt Creator and open your .pro file. Qt Creator will ask you to reconfigure your project. Accept that.
Now you can debug again, or at least I could; the problem happened to me when I had just updated Qt Creator.
I had a problem in windows 7 but I've solved it:
Download Windows driver kit
https://www.microsoft.com/en-us/download/details.aspx?id=11800
Add your debugger
Change auto-detected kit debugger to your added debugger
I installed Debugging Tools for Windows and the debugger appeared under Manage Kits > Build & Run > Debuggers but it didn't added in the kits so I had to go to Manage Kits > Build & Run > Kits then select the desired kit and under Debugger I had to select the debugger. Initially the debugger is set to "None".
Answering the title of this question, not the person asking it.
I had the exact same error message on arch linux 64 trying to compile for arm android.
First I ran the gdb debugger in the command line to get the root issue:
~/tools/android/android-ndk-r12/prebuilt/linux-x86_64/bin/gdb-orig:
error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
libncurses is the issue! (As of 6/24/2016) Arch linux is on ncurses 6.0-4. Later you'll also find libtinfo.so.5 is missing.
At this point, the method for fixing the problem is up to you; I don't like using a bunch of AUR repos, so I executed a simple hack. We're forcing the library linkage that was in libncurses 5x to point at 6x.
Please ensure you don't overwrite anything before running these commands
cd /usr/lib
sudo ln -s libncursesw.so.6.0 libncurses.so.5
sudo ln -s libncursesw.so.6.0 libtinfo.so.5
Re-run your arm gdb, and it should work.
I have a really weird problem here.
I am using Qt 5.5.0 with mingw 4.9.2 32bit and QtCreator and Git on Windows 7.
My Project builds just fine but when I run the executable either outside or inside QtCreator the process appears in Task-Manager/ProcessExplorer but the Window itself does not show up and when I try to kill the process it does not react. Process Hacker can't terminate the process either. The QtCreator debugger waits in vain for the process to start. I have to reboot the PC to kill the process.
Thing is that it worked a few days ago and other qt projects work fine, too. I had the same issue on a different PC. I couldn't find the issue so I reset it to stock; I can't do the same with this one.
What could I have possibly done to cause this?
OK, I found the issue. It was my antivirus software. I am using avast free antivirus and somehow it caused the issue without telling me. Excluding the build directory from the scans solved the issue.
Thanks to Paul for the answer!