Eclipse CDT - Set include directories globally - eclipse

I know I can add directories to search for includes, for each project.
Is there any way to add them globally, i.e., for any project (currently existing, or to be created)?

Related

Eclipse Plugin's plugin.xml file doesn't add a menu or export wizard specified in plugin.xml

I am trying to add a export action to the Eclipse File > Export dialog. I've tried adding it through plugin.xml (see below update about dropins vs plugins folder) and while it works in a Mars 2 (Eclipse Platform / RCP version 4.5.2) instance it does not work with version 4.6.2 where I'm intending to use the jar. Previously the plugin.xml did not work also for a menu item, however I was able to do that programmatically (but seemingly not add an export wizard programmatically).
Update 2: It seems it may have to do with the eclipse's configuration config.ini file or Equinox Transforms (see https://wiki.eclipse.org/Equinox_Transforms). I think it may be the later because the plugins run and you can add ui elements later (like the aforementioned menu) with programming, but not with the plugin.xml. Also the config.ini makes reference to the Equinox Transforms class.
Update 1: The plugin.xml not running seems to be related to something to do with the dropins folder.
Foo.jar provides some exports and was provided by the vendor through a P2 update site I believe and exists in a plugins folder.
When I rename Foo.jar to Foo.jar.old and re run the app (with -clean) the exports are removed (Good)
When I name it back to Foo.jar in the plugins folder it re adds the exports on startup (Good)
When I move Foo.jar to the dropins folder the plugin DOES LOAD (it's listed in Help > Installation Details > Plugins), however the export options specified in the plugin.xml are not populated. (Bad)
Is there a difference between the eclipse dropins folder and the eclipse plugins folder of a P2 update site?
I have since confirmed it was a Equinox Transform in use (it shows up in the plugin list). Upon searching for jar files mentioning transform one had the xlst files in the jar and unzipping them, editing them, rezipping them to a jar file and replacing the original fixed the problem (I did have to run eclipse.exe -clean otherwise it did cache the old one and seem not to work).
Also of note look at the config.ini it should make reference to Equinox Transforms.

Disable auto discover of include paths in Eclipse

I have a self contained project where every included file is within the project itself.
In the project properties -> "C/C++ General" -> "Preprocessor Include Paths, Macros etc." -> "Providers" I disabled the entries I don't need, but something re-enables the "CDT Cross GCC Built-in Compiler Settings".
Is there a way to permanently disable this option?
I want to keep the indexer working, and also I have some entries in the CDT managed build entries so its not an option to get rid of the build configuration (I do not build/start the build of the project from Eclipse).
The automatically added includes conflicts with the files within my project messing up the indexer (it adds the MinGW includes).
I am using Eclipse Oxygen on Windows 7.

Eclipse / Aptana - exclude folder from 'Connections' sync

I have a PHP project in Eclipse (with the Aptana Plug-in) that I deploy to a number of different hosts using the 'Connections' Sync mechanism. The problem is that in addtion to all the common code each site's 'instance' of the project contains a host specific folder tree that can contain a large number of files. Each time I run 'sync' I have to manually check 'skip' for the host specific folder and all of its children.
Is there any way I can config sync to ignore this folder?
I've looked through the include/exclude filter stuff and various entries in Stackoverflow for 'exclude files/folders' but they all seem to relate only to repository syncs (GIT/SVN ...), validators, builders etc
jon
I hope this functionality exists in Eclipse with the Aptana Plug-in, I am using Aptana standalone.
I think the option you are looking for is called cloaking. You can set up name patterns for cloaking under Window > Preferences > Aptana Studio > Publishing. Here you can add file naming patterns to be excluded from all publishing - other projects will also ignore these file name patterns so use caution. I prefix files and folders with an underscore when I don't want them syncing and then just use _* in this preference.

Team->Commit in Eclipse shows resources from a symlinked directory. How to ignore?

When I want to commit my project into svn, Eclipse displays a list of files in our tmp directory. Eclipse offers the possibility to add all these files to svn. But I don't want that, I want Eclipse to ignore the entire directory.
About the project
Our project contains a symlink 'tmp' where all our cache files are written to:
lrwxrwxrwx 1 tijmen tijmen 11 Oct 14 11:28 tmp -> ../tmp
The tmp symlink is already added to svn:ignore. The ../tmp directory is not in version control.
The ../tmp directory contains a lot of cache files (837 as of now). Every time I do Team->Commit it lists all the cache files as New in the Content column. Because the list is so long it is very hard to find the files I actually want to add and/or commit.
Is there a setting in Eclipse which enables me to ignore contents of a (symlinked) directory in the Team->Commit view?
I found a solution.
Right mouse on project -> Properties -> Resource -> Resource Filters. Here I created an exclude filter to exclude symbolic links. Luckily I have only one symbolic link in this project. For other projects a stricter filter can be created.
Add the selected tmp symlink to the svn:ignore property of its container folder. If it has not been added to the repository at all, simply right click on the folder, and select Team/Add to SVN Ignore (or something really similar name).
Otherwise you might have manually remove the existing folder, and add the corresponding property to its container folder.
EDIT: BTW. I am using the Eclipse Subversive plug-in; if you are using the Subclipse plug-in, search for option setting the svn:ignore properties.

Why is eclipse trying to compile files not in my build path?

I have a rather large project which contains a number of third-party dependencies which are linked via svn:externals. These include tomcat and blazeDS, which are packaged by our installer via ant. The problem is that these projects contain dozens of sample JSP pages, and eclipse chokes on them when trying to build the project, producing hundreds of errors.
Our project setup is something like this:
src/
main/
test/
third-party/
blazeDS/
tomcat/
etc.
Now, in eclipse, my project's build path is set to only include subfolders in src/main and src/test. Yet, for some reason, it still tries to build everything beneath third-party. I have clicked on third-party and selected "remove from build path", but this had no effect. I even tried adding the third-party folder to the build path, and then excluding "", "/*", and "**/*.jsp", but again, to no effect.
What is going on here?
Edit: Thanks for the suggestions, though unfortunately, they don't seem to fix the issue. I don't have the CheckStyle plugin installed (I'm using Eclipse 3.4.1 with the only custom plugins being subclipse and flex builder), and I tried disabling all extra builders except for Java, but the errors are still being thrown.
I usually have this kind of issue with CheckStyle plugin, where you need to specify in its properties (right-click on project -> Properties -> CheckStyle):
"Exclude from check Files non located in a source directory"
Otherwise it does analyze (and reports warning/errors on) files which are not candidate to be compiled in the first place.
Couple of other suggestions:
try restarting your eclipse with the -clean option (eclipse software version of 'did you reboot it ?' ;) ). Beware it can reset your workspace perspectives, so you may want to try that with a copy of your workspace instead.
try deleting your project (your workspace reference of your project, not its actual content), and reimporting it (beware of your custom launchers, they may get removed in the process).
check if you do not have any linked directory within src or test, which would point to thirdparty(/**): that would explain the unwanted compilation.
It could be that your eclipse project is configured to have extra Builders. You can check that in the project's properties (right-click on project -> Properties -> Builders).
In my case it was because there was a reference to the file (which I had excluded from the build path) in another file which was in the build path. I wanted to exclude SegModel.hpp from the build path, but in another file, I had specified template short K::KEstimate<SegModel>(SegModel& m, short stepCode);