I am using Eclipse Indigo with CDT 8.0.2 to browse through the code of a C++ library. The library is also installed on my system. Many times when I go to a declaration of a function, Eclipse finds the declaration in a file under /usr/local/include, even though the header file is also in the project.
Can I avoid this behavior? For now I'd be okay with limiting the indexer to index only files within the project. In the Indexer Preferences, I unchecked Index source files not included in the build without success.
Related
I have a small problem with my Eclipse IDE PyDev plugin - when I'm developing a program using Python with libraries in *.pyd format, I can't go to definition, because It's binary format. But there are corresponding *.pyi files with source code. How to "force" PyDev to use *.pyi files instead of *.pyd files for Go To Definition?
I have a Maven project with Scala and Java. I generally develop it using Intellij IDEA, however, I sometimes open it in Visual Studio Code.
Whenever I do that, it automatically adds .settings directory, .project file and .classpath file to the root of each module in the project.
This is seemed to occur due to the Language Support for Java by Red hat extension.
I would very much like to avoid this, how would I do that?
The Language Support for Java(TM) by Red Hat (aka vscode-java) extension generate those Eclipse files, because, under the hood, a customized, headless Eclipse process (jdt.ls) is providing all the Java support. You can not remove these files, if you expect proper Java support by this VS Code extension.
So your alternatives are:
add these files to your .gitignore (if you're using git, else, ignore them from whatever SCM you use)
disable or uninstall vscode-java and use a different Java extension in VS Code
I'm using the JavaCC Eclipse Plug-in 1.5.30 with Eclipse Luna Service 2(4.4.2).
When I use JavaCC to generate java files from the st4tic.jtb program grammar, Eclipse seems to completely ignore them when I do a file search.
In the navigator view, all of the generated files have appended to their names e.g. NodeList.java <st4tic.jtb>
There is an option for the plugin to not mark generated files as generated.
I've recently been trying to setup a little toolchain for something with Eclipse CDT but I'm being driven insane by the default behaviors of Eclipse. It's just so against the grain of other IDEs for C/C++.
Is there anyway to disable the automatic searching of folders in the project directory for the source files? I want to manually add the files for it to compile instead of having to manually exclude all the files I don't want it to compile between multiple configurations.
you can use your own makefile instead on relying on the eclipse auto generated makefile
I have used Eclipse Indigo (C/C++) for sometime along with PyDev Plugin (for Python). As I messed up with the IDE (tried to tweak some core files, for fun!), I thought to install a fresh one and this time I downloaded Eclipse Indigo (for Java).
Eclipse (C/C++) was placed in C:/
Eclipse (Java) was even placed in C:/
Now when I opened Eclipse (Java), I observed two things:
The Eclipse's title bar still showing <C/C++ Eclipse>
There was a python's project file still opened up which I worked on Eclipse C/C++ IDE. Also, there was an PyDev's error popped up (mentioning it wasn't installed).
I have verified "Installed Plugins" list and didn't find any plugin related to C/C++ or python.
Now, I have got one question:
As I searched over google and found that Eclipse doesn't store anything beyond its directory, How does this above things are showing up??
There might be some Temp/ Cache files stored. However, I searched my drive with "Eclipse" and "PyDev" as keywords and found nothing.
I even searched for registry keys but couldn't find anything.
What exactly is happening and how do remove Eclipse completely?
TL;DR: using the new Eclipse (Java), select "File > Switch Workspace... > Other...", and create a new directory (e.g. java-wks) for all projects you will do using the new Eclipse.
The long explanantion is that Eclipse stores data in two locations:
The eclipse installation directory itself: contains the plug-ins you install (including the ones already installed in the package you downloaded) and some runtime configuration parameters (see eclipse/config.ini) related to how Eclipse itself should run (e.g. where to find the JRE to execute Eclipse itself, how much memory to allocate etc.)
The workspace(s), where your data (projects and source code) and all personal configuration parameters are stored. This is where Eclipse remembers where your source code is, which file(s) where opened when you last exited, which perspective was active (in your case C/C++ Eclipse), your preferences, launch configurations, breakpoints, etc.
For each Eclipse installation on your system (eclipse folder), you can have as many workspaces as you want (it helps to isolate work). There are various ways to select the workspace location: using the -data <path-to-workspace> option on the command-line, using the popup Eclipse normally shows when starting up (but you may have disabled it), or using "File > Switch Workspace...".
You can also use the same workspace from different Eclipse installations (though not at the same time), but things will not work well if you have different plug-ins installed in each: if one installation stores in the workspace "this is a Python project, and the current perspective is C/++", and the other installation does not have the Python and/or C++ plug-ins installed, it will not known what to do with these info. This is why you see the errors you reported.
For your case, my guess is that under Windows the default workspace location is somewhere in your home directory, and the new (Java) Eclipse is using that, but failing to make sense of the Python and C++ related preferences and projects the previous Eclipse stored there. You need to use a fresh workspace not "polluted" with Python and C++ stuff if you want the Java Eclipse to work without errors (or install the Python and C++ plug-ins in the new Eclipse). You may want to enable the Prompt for workspace on startup preference (in "General > Startup and Shutdown > Workspaces") if it is not to control this easily each time Eclipse starts.