After upgrading from Eclipse Neon to Oxygen I noticed that I can no longer navigate around the code by clicking on definitions while holding the Ctrl key down. The indexer itself works fine, and I can still jump around by pressing F3 or using the context menu.
I am using Eclipse CDT with C++.
The following screenshot proves that the feature is enabled:
What am I missing?
You're probably running into bug 517610. Note the following workaround from the bug:
To work around the problem, you can disable the Change Log hyperlink
by going to Window > Preferences > General > Editors > Text Editors >
Hyperlinking, then untick "Changelog Detector".
The bug fix is scheduled for Oxygen.1, which will be released on September 27th 2017. Alternatively, you can update to the latest development build (6.1.0) of Linux Tools (which is the component that contained the bug) via the update site http://download.eclipse.org/linuxtools/update/.
In addition to the first solution, increase the "Maximum number of tokens per translation unit" in your Eclipse.
Related
I have recently installed Qt Creator 4.8.0 based on Qt 5.12.0 and I have it configured like in the image below. However, I haven't managed to start the debugger. As it can be seen, the debugger is correctly set for this kit, the one I'm using right now.
Any solution?
Thanks!
Wow! I found it!!! Here in the tab "projects", there are several build and run configurations. Despite you select a default kit, the final one being executed is the one in black under this tab.
Finally I disabled all of them except the one that was properly configured in the Kits window and it worked. I hope this information is helpful for someone. I don't think that part of the configuration is clear.
I got the same error, but in my case I was using the MSVC compiler and the kit didn't manage to find the CDB debugger. I was able to fix it by going to "Add or remove programs" -> "Windows Software Development Kit" -> Modify -> Change -> Debugging Tools for Windows.
In my case it was needed to select "Enable C++" under Debugger settings
screenshot
The same dumm error QT creator shows when you simply don't have gdb installed.
Worked in my case ;)
I had the same error in MacOS, debugger suddenly stopped working (LLDB debugger worked in XCode but not Qt Creator).
In this case, I reinstalled Qt Creator and reinitialized the config by removing the .config/QtProject directory located in homedir. This solved the problem.
I had the same issue when Qt Creator didn't recognized the path to the Debugger. Due to some reason it showed multiple Auto-detected Debuggers at the same location. And on the top one of the list with the red error indicator.
see
Projects->Manage Kits...->Debuggers
I removed the erroneous Debugger and restart the Qt Creator.
I wonder if there is a support for C++ in Netbeans 9. This link shows C++ on screenshot (when creating new project). However, after installing, I don't have one.
I wonder if there is a support for C++ in NetBeans 9.
The answer to that is definitely no, and definitely yes...
No, in the sense that the use of C++ on NetBeans 9 is not currently supported by Apache, and it is done at your own risk. NetBeans is currently being handed over from Oracle to Apache, and they haven't got to the C/C++ part yet. See What's Happened to My Favorite NetBeans Plugins? for more information.
Yes, in the sense that it is technically feasible to do it; the NetBeans 9 IDE allows you to use C/C++.
This is what you need to do:
Step 1 of 2: Make C/C++ available as a plugin.
Tools > Plugins > Settings tab > click the Add button.
On the Update Center Customizer screen:
Enter some value in the Name field (e.g. "My plugins"),
Enter http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz in the URL field
Click the OK button.
This should create a new entry in the Configuration of Update Centers list in the Settings tab.
Checking that new entry should instantly add plugins to the Available Plugins tab.
Click the Available Plugins tab, then click the Category column to sort the entries by category.
The Name of the entry at the top of the list should be C/C++. If so, you have successfully made the plugin available:
Step 2 of 2: Install the C/C++ plugin.
Check the C/C++ entry shown in the screen shot above, and then click the Install button.
Follow the wizard's instructions. The plugin will be downloaded and installed, and you will be required to restart NetBeans.
To confirm that C/C++ has been installed, click Tools > Plugins > **Installed tab. You should see an entry for the C/C++ plugin you just installed.
Also, verify that you can now create a C/C++ project through the Project wizard:
Notes:
The finer details on configuring C/C++ on NetBeans 9 (Tools > Options > C/C++) are unchanged from NetBeans 8.x. Refer to Configuring NetBeans IDE 8.0 for C/C++/Fortran for that.
Much of this answer has been copied from an answer I gave on problems with Tomcat on NetBeans 9, but the details are sufficiently different to merit a separate answer.
Netbeans 10 and 11 - adding C / C++ also works in the same fashion.
In Netbeans go to Tools->Plugins->Settings
Entry NetBeans 8.2 Plugin Portal is already present.
Click the checkbox next to this entry.
Switch to Available Plugins tab, click Check for Newest.
C / C++ is now on the list.
Computer that this is done is on Windows 10 x64.
You have to install C++ plugin (Tools -> Plugins)
I have a problem with VS2013. I'm trying to write a program in vc++ using opencv and in vs2013 update 4 IDE. the problem is as I just type these lines, my computer freezes. infact the hard activity runs to 100 percent and never stops untill restart. even when I (hardly) close VS and even when I logged off, hard disk activity is still at maximum. the code is:
#include <iostream>
#include <stdio.h>
#include "opencv2/core/core.hpp"
#include "opencv2/features2d/features2d.hpp"
It seems that the last line makes the problem.
FYI I have tried and run lots of OpenCV examples in VS2013.
And when I tried the code above on VS2012 on another computer it works well, but on VS2013 on another computer it again freezes just like my computer.
So what's wrong here?
The problem may point to several performance issues in VS2013, please try each one of the following separately until overcoming the issue:
Disabling Synchronized Settings: Go to Tools -> Options -> Environment-> Synchronized Settings and remove this option by unchecking the checkbox.
Set Current source control plug-in to None: Tools > Options > Source
Control
Clear the "Use hardware graphics acceleration if available" check
box to prevent the use of hardware graphics acceleration : Tools -> Options -> Environment-> General , make sure "Automatically adjust visual experience based on client performance" is cleared too.
Note: You can select or clear the "Enable rich client visual experience" check box to make sure that rich visuals are always on or off, respectively. When this check box is selected, rich visuals are used independent of the computer environment. For example, rich visuals are used when you run Visual Studio locally on a rich client and over remote desktop. it may help too.
Try deleting the solution's .suo file (it's next to the .sln file),
closing and re-opening Visual Studio
Background:
I'm a big fan of using Codeblocks to do C++. I have just upgraded to Ubuntu 14.04 LTS and installed Codeblocks via the Ubuntu Software Centre.
My Problem: All is going great, apart from one minor thing which is missing. When I double click on a variable, other instances of that variable used to be highlighted too. This was an extremely useful way I debugged my programs. But it isn't here on the new version for some reason.
I would like the feature shown in the screenshot below to be set. Where is the option?
Please can someone help me out, maybe there's an option I'm missing?
Install the contrib plugins for Code::Blocks IDE (codeblocks-contrib) to enable occurrences highlighting in Code::Blocks.
sudo apt install codeblocks-contrib
In Code::Blocks select Settings -> Editor -> Occurrences Highlighting (scroll down in the pane on the left side to find it) and then put a check mark in the three checkboxes under Highlight occurrences of selection as shown in the below screenshot.
The three checkboxes to select are:
Highlight occurrences
Case sensitive
Whole words only
Then click the OK button to apply the changed settings. You can also put a check mark to the left of the two settings under Permanently highlighted occurrences in order to apply these settings.
karel -- Thank you very much for your answer. I believe this will be the thing which will solve most people's question.
For completion, I would like to document my different answer (for other forum users).
I simply had to install the optional extras on the Ubuntu software centre alongside the Codeblocks installation. The menu "occurence highlighting" did not appear without doing this.
Best wishes.
I remember from some time ago that Eclipse had auto-complete when you type, and now I can only get it when pressing Ctrl + Space. I already checked and don't have any unresolved dependencies, I can see all the auto-complete choices when pressing Ctrl + Space, but that's not something I like to do every-time... Can someone point me in the direction to get auto-complete back? (Using CDT C++)
At some point recently (not sure but since March 2013?) my Eclipse CDT stopped auto completion. I figured out that at Editor->Content Assist->Advanced checking Parsing-based Proposals lets auto completion work on my machine.
Ubuntu 12.10, Eclipse 4.2.2, CDT 8.1.2
This snapshot shows Task-Focused, which I don't see on my another Eclipse instance. In that case I just checked Parsing-based Proposals and completion still works.
This question is so valid even in 2018 with eclipse photon.
1) Go to Window > Prefrences > C/C++ > Editor > Content Assist > Advanced.
2) Check "Parsing-based proposal(Task-focused)".
3) Bind a key now by pressing "Ctrl + Space".
I had a problem with Eclipse Juno (OSX Java "1.6.0_33") where the autocomplete (and save key binding) wasn't working properly. Googling I found this: Eclipse JUNO doesn't start
Updating my Mercurial Plugin to the latest (1.9.1) fixed both these issues for me.
Very weird.