System: M1 mac with 16G of memory, OS Ventura.
My large application with codelite builds fine with g++ and comes up and runs. There are features that don't work correctly, so I need a debugger. When I try to start either lldb or gdg either something flashes on the monitor and stops or simply just does nothing. Codelite has worked well for me for 13 years. I hope someone has a similar problem. My only choice now is to use lldb from the command line, and this is difficult for me.
I changed debuggers frequently tried to acquire an older version of codelite, asked for help on ther codelite forums and got no response.
CodeLite no longer supports lldb directly (on all platforms).
It has moved to use the new DAP (Debug Adapter Protocol) method of debugging code.
On macOS, you should install lldb-vscode via brew:
brew install llvm
In CodeLite make sure that the DebugAdapterClient plugin is loaded: Plugins -> Manage...
Force a new scan: Settings -> Debug Adapter Client and CodeLite should detect the new debugger
In your project, change the debugger to lldb-vscode
You can read more about DAP integration here:
https://docs.codelite.org/plugins/dap/
Related
I want to build Qt 5.4.1 form source with MSVC2013 under windows 10 condition.
However, when I do the configuration, it just stopped without any errors.
I downloaded qt-everywhere-enterprise-src-5.4.1.zip and unzip it.
I installed active perl ver5.2.6, python 3.7.6, ruby devkit 2.7.6 and added there path to environment variables.
And then, in the Developer Command Prompt for VS2013, typed
path_of_src\qtbase\configure -platform win32-msvc2013
then it shows me the following messages and just stopped configuration.
+ cd qtbase
+ ...\qt-everywhere-enterprise-src-5.4.1\qtbase\configure.bat -top-level -platform win32-msvc2013
Qt: Untested Windows version 10.0 detected!
This is the Qt
(and I even did not put -top-level option)
I think some words and process should be followed after 'This is the Qt' sentence, but there wasn't.
Also it doesn't show me any error messages so I'm stuck in a labyrinth now...
Please let me know if you have any idea or need further information.
Thank you in advance.
Best wishes,
JESuh
When I select "Debug > Start Debugging" I'm prompted for the environment and I select ".NET Core" but then nothing happens.
If I type"dotnet run" in the terminal window the program runs just fine.
"Help > About" displays the following;
Version: 1.33.1 (user setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134
EDIT:
I've tried the 32 and 64 bit versions of .NET Core and the corresponding System and User versions of vscode. In each instance I've tried running as Administrator and normally. I just don't think it's going to work on this machine.
I've done a similar install on Ubuntu and it worked the first time.
EDIT 2:
I finally managed to see this error, but I haven't been able to resolve it.
Cannot create .NET debug configurations. The OmniSharp server is still
initializing or has exited unexpectedly.
The debug freature is provided by the C# (ms-vscode.csharp) extension that uses omnisharp as back-end. So debug not working is probably because omnisharp is not working properly, which is maybe your omnisharp is still downloading (The download source is sometimes unstable) or there are some problems in your project files (csproj and sln files), or the SDK environment is not correctly configured.
If omnisharp is running, you can see the Omnisharp Logitem in the output window, otherwise check the C# item, which may includes the downloading status of omnisharp. Check them and you may get how it is not working, or just paste the exact output logs for help.
I had a similar issue when I hit f5 on a VSCode .net project. It asked me to select the debugger (.net core 5+ or .net framework). However nothing happened no matter what I tried. Clicking on the Debug icon on the left revealed a link to create a launch.json file. Clicking that link created the file and then I was able to debug.
enter image description here
I am trying to install kde-connect following this.
Although my kubuntu version is 14.04, I wanted to compile them so that I can have the latest version. But when I followed the instructions to compile, i get the following error.
-- Found Qt-Version 5.2.1 (using /usr/bin/qmake)
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
QT_QT_INCLUDE_DIR
used as include directory in directory /home/vinaychandra/Downloads/t/CMakeFiles/CMakeTmp
CMake Error: Internal CMake error, TryCompile configure of cmake failed
CMake Error at /usr/share/kde4/apps/cmake/modules/FindKDE4Internal.cmake:1311 (message):
Unable to compile a basic Qt application. Qt has not been found correctly.
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindKDE4.cmake:95 (find_package)
CMakeLists.txt:7 (find_package)
Please point out how to correct this.
I have tried giving -DQT_QT_INCLUDE_DIR=/usr/share/qt4/
then it tells that You must build your code with position independent code if Qt was built with -reduce-relocations.
Your cmake by default uses a different QT version.
So, you must explicitly tell him which version of QT he have to use for this job.
This one
-DQT_QT_INCLUDE_DIR=/usr/share/qt4/
Is wrong because you mustn't give QT position explicitly.
All you need is to use the right qmake.
So, give'em this flag and you'll be happy!
-DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt4
Since most of kde applications are not ported to Qt5, you need Qt4.x for building kdeconnect(don't know x, mine is 4.8.6).
Also Qt4 installer is not available (I think !), so you have to build it also from source. Building Qt4 is quite easy, just download the source and run the usual commands.
After building it, it qmake name will be qmake-qt4 in /usr/bin.
So for building kdeconnect, first run its cmake, then a Cmaketextcache.txt file will form.
In that change the path of qmake (i.e somewhere written /usr/bin/qmake to /usr/bin/qmake-qt4) and also the path of qt include dir to (I think /usr/include/qt5 to /usr/include/qt4), and run the cmake again.
If some packages are missing, then you have to install it.
But with the above changes, you will get a make file to install it.
Unfortunately, the cited documentation is lagging behind the current state of kdeconnect. I ran into similar problems but I managed to solve them by installing the following required packages from the Kubuntu repositories:
sshfs
libfakekey-dev
libxtst-dev
libqca2-dev
libqjson-dev
I trust these are all of them. I installed kdeconnect from the latest git commit and it seems to run fine.
This answer comes a bit late, but this is the first Google search result for the question. In systems with qtchooser (Kubuntu, Ubuntu at least), this can be fixed by running first:
export QT_SELECT=qt4
This makes all of the Qt build tools to default to the Qt4 version instead of Qt5. You can check which Qt version is active by running:
qmake --version
Try kde connect install on ubuntu: https://fazlerabbi37.github.io/blogs/install_kde_connect_in_ubuntu_18.04.html
(in 18.04 & 19.04 it works with simple sudo apt install kdeconnect
Install kde connect on android device (google play store is where I installed from)
Invoke kde connect from desktop
Invoke kde connect from android and search device.
Your ubuntu will be found / initiating a search from desktop results in android phone pulled up for pairing
Accept pairing request
Provide access to folders
Try clicking on a video/image file for transfer
I could see the new file transferring in /Downloads folder of desktop
allowing/disallowing desktop to access sms, notifications etc are now a choice
Note: Pl treat this with pinch of salt. This appears very simple, effective for a main reason it worked for me in no time.
I am trying to install MacVim in my Macbook Pro from Homebrew. However it "got stuck" at
xcodebuild -project MacVim/Macvim.xcodeproj ARCHS="x86_64" ONLY_ACTIVE_ARCHS="NO"
for nearly 6 hours. Last time I remember building from source that took me so long was the Open Office.
By the way. I am running Lion. I know there is no stable version of MacVim for Lion yet but I guess this shouldn't be a problem building it. I have Xcode 4 installed with Command Line Tools.
Am I missing something?
Thanks in Advance.
Problem solved. What happened is that I installed the command line tools for xcode but its path was not properly configured. For example, to compile MacVim it required xcodebuild to run. The only reference for xcodebuild I found in my system was in /usr/bin so I set the path to that location. Even though xcodebuild was being found by make, it would get stuck forever and not returning any erros (weird). I tried to build other application purely based on gcc and it got stuck with no errors too. Finaly I found the correct path for command-line tools for Xcode 4.3. The code to set it up is:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
source: http://jeffreyearly.com/2012/02/28/broken-command-line-tools-clt-in-xcode-4-3/
I'm trying to install Qt-4.6.0-wince on XP and Vista. I read the instructions and follow it to install.
However, I can't install it successfully due to some fatal errors on all of the two machines. I think the problem is that qconfig.[h cpp] files are not created automatically during the configuration.
I already report about this problem, so you can see the more information here. However, it is still remained as unresolved.
Anybody here who has been installed it successfully?
#KernelJ I believe the original poster is using the correct install distro - the final product will be cross compiled from Win32 to WinCE; as is pointed out in the Qt for Windows CE Requirements.
#Brian, Unfortunately, I can't answer your original question - I have had unrelated trouble with the WinCE distribution myself and am working the issues now. However, I can provide some help: I was able to get the Qt Everywhere 4.6 to cross compile on my Win32 (XP) host for WinCE. I used the commercial version, but here is a link to the Open Source Qt Everywhere 4.6 package. As is pointed out in the nokia instructions, make sure to use the Visual Studio command prompt, get your environment variables ironed out, create a custom mkspec (if you have to), and keep a close eye during the configuration for any warnings.
Good luck.
Qt-4.6.0-wince, as is implied in the name and said explictly on the page you linked, is for Windows CE, NOT for Windows XP and Vista!!!
Nokia have released a nice software development kit for Qt which you can download here. It is very impressive and powerful!
I got things running as compilable (and running on emulator) with VS 2008, so your milage may vary:
Make sure the PATH variable points to \bin
Open a command prompt (using the Visual Studio Command Prompt)
Run the vcvars32.bat file (in C:\Program Files\Microsoft Visual Studio 9\VC\bin) folder
Cd into the qt folder
Run this: configure -no-sql-sqlite -no-qt3support -platform win32-msvc2008 –xplatform wincewm50pocket-msvc2008 -no-phonon -no-phonon-backend -no-webkit (building for WINCE 5.0, and all the '-no-...' makes it build faster, removing stuff we don’t want)
The setccepaths script provided sometimes doesn’t work. I used checksdk.exe –script temp_script.bat (It creates a script, the default is for Pocket PC SDK 5)
Run that script you just created (the temp_script.bat thing. It sets up environment variables.
Run nmake
*whew*
and good luck.