Errors running builder 'CDT Builder' on project 'proj1' (eclipse CDT) - eclipse

I have a question about how to import an project that contains an existing make file into eclipse.
From reading the eclipse documentation it seems that i should use a "Makefile Project"
Is this correct?
If so then the import of the project files seems ok, but when I run build I get:
Errors occurred during the build.
Errors running builder 'CDT Builder' on project 'proj1'.
Internal error building project proj1 configuration Default
java.lang.NullPointerException
Internal error building project proj1 configuration Default
java.lang.NullPointerException
ok. So I i assume that i am getting this because the build target points to nothing. So i got to Project-> Properties -> C/C++ Build and all the "builder settings" are grayed out.
My next attempt was to go to Project -> Make Target -> Create. What i see here is:
Target name:
Make Target:
Use Builder settings:
I made several attempts at putting values into these fields and running make again, but I get the same error.
When using eclipse CDT in the past i have always created the project myself so eclipse handled the whole make thing for me. But I am at a loss of how i actually tell CDT what make file to use or why I am receiving the above error message.
So i gues my question is if i want to import a C project with an existing file how do i tell eclipse what make file to use? In the flow i chose these options seemed grayed out.
I tried looking this up on stack exchange, but have not found an exact match for my situation
Thanks in advance.

It looks like something went wrong with your import. You should have imported your code via Existing Code as Makefile Project. The build command can be defined in the project-properties dialog, under C/C++ Build, Behaviour tab, in case you have a specific situation.

Related

The project was not built due to "ProjectXX does not exist".

I am trying to set up a workspace in MyEclipse. And I am getting 20 errors with the same description as below.
Description Resource Path Location Type
The project was not built due to "ProjectXX does not exist". Fix the problem, then try refreshing this project and building it since it may be inconsistent ProjectXX Unknown Java Problem
Now I can see that this project, ProjectXX is clearly in my workspace and it is a EAR project. My team does not face this issue in their MyEclipse/PC.
I dont know why, but this resolved my issue. I selected the option to import existing Gradle project into workspace and then gave the exact root folder of the project and then the errors were gone.
I had the same problem and the solution was to deactivate the "Java Builder" property. To do it, just open the project properties with right click, go to "Builders" and deactivate "Java Builder". You can now delete the errors, validate the project and the problem is never seen again.
Thanks to #Tony Weddle for the hint "the EAR is not a Java Project".

Eclipse says there's an error, but where?

If I do Project -> Clean and then Build, everything is fine, but if I try to run this Android-project, a dialog comes up: "Your project contains errors. Fix them before running application", and there's a red cross on the project name.
There's no cross on any item in the project tree, and nothing in Console view or LogCat view. So, where's the error?
The only difference for this project and an earlier working version was that I removed a link to an external .jar file, created folder "lib" and put the .jar in there, and added that .jar to the build path. The .jar is the exact same as the external referenced.
You may need to Refresh your project in order to see the errors. Also, bring up the Problems tab for more specific information (Window > Show View > Other > General > Problems).
Eclipse shows the Errors in the Problems View.
It's difficult to guess but I would check the build path (right click the project and see), if some entry is missing there then there can be this error sign. Another reason of this red error sign is, if this project includes some other java project in path which has any errors (compilation or build path), then it will also display errors.
I had this error when I deleted a library, but did not remove it from the build path. Go to Properties - Java Build Path - Libraries. And see if you see something like "can't find library" and remove it.

Why I cannot use JSLint eclipse plugin by Rockstartapps?

I am running eclipse (Eclipse for PHP Developers).
After installing JSLint plugin from Rockstartapps (http://update.rockstarapps.com), the plugin don't validate.
When I am trying to apply validation to particular file (Right click on the file -> Rockstarapps -> Validate with JSLint...) it does absolutely nothing.
When saving a file it throws eclipse error:
Errors occurred during the build.
Errors running builder 'Rockstarapps JsLint Builder' on project 'testapp'.
java.lang.NullPointerException
Any clue why this happens?
Update
Found a very good replacement solution. Works completely the same as plugin by Rockstarapps worked before, perhaps rules are even a bit updated.
Looks like a bug in that plug-in.

Red exclamation mark in Eclipse with mercurial

I have imported a project with Mercurial (hg clone ...).
When opening it with Eclipse, a red exclamation mark appears by the project's name in the Project Explorer, and it cannot be built. Silly messages like "import java.util cannot be resolved" appear, and errors in files are not marked in the Package Explorer.
How can I resolve this?
Check the problem view. By exclamation it is usually means a problem with build path
Check the Build Path of the project by right clicking the project and select Build Path -> Configure Build Path.
One problem I often encountered is different people using different Java SDK and so when the exact SDK is not available in your machine, you need to change to your Java SDK (via JRE System Library -> Alternate JRE). A better way to avoid this problem is to always select the JRE System Library from Workspace default JRE or Execution Environment.
I solved the problem by adding the external .jar file in to my project.
RightClick on the project -> Properties -> Java Build path -> libraries tab -> Add jar
Select your jar file and added it
Thats it the red ! mark gone.
Some times it happens that you have added a jar file earlier but currently not using it. Then after some time you delete the jar file from your system. But since you are not using the library file, so you will not get any error.But then you will see the red exclamation mark for the project. So all you need is to remove the added jar from the Build Path.
Done.....
The Java Runtime Library was defined wrong for the pulled project.
It had to be reset under Project | Properties | Java Build Path | Libraries.
It means there is a problem with the build path in your project. If it is an android project then it mostly means the target value specified in project.properties file cannot be found. This can also be caused because of other kinds of built problems. But it is shown mostly for built problems only. See here for more details. It is about built error decorater seen in eclipse.
An extract from that page:
Build path problems are sometimes easy to miss among other problems in a project. The Package Explorer and Project Explorer views now show a new decorator on Java projects and working sets that contain build path errors:
The concrete errors can be seen in the Problems view, and if you open the view menu and select Group By > Java Problem Type, they all show up in the Build Path category:
I figured out each time i am trying to import a library into my android project, i have a red exclamation mark with both ActionBarSherlock and Facebook libraries
This is how i solved it:
After adding the library into your project "project properties->Android->Librairy->add"
If you are using Eclipse, all you have to do is to clean your project and build all your workspace:
"project -> clean... -> "clean selected project" -> build the entire workspace
For me, the problem was a simple one - the reference project was compiled in 1.5 and my project 1.6. Matching the two solved the issue.
Right-hand-click on the project, select properties, select java compiler.
This is how I solved this problem:- Right-Click to project->properties->Java Build Path->Libraries(tab)->Remove the Jar which is already present there with a Path given along.

Failing to add a builder to my eclipse project

I am trying to add a new builder to an eclipse project and I am having a problem.
The new builder is an external program.
This is what I have done:
I have created a new program configuration in the external tools.
After creating it I have tested it by making it run - it worked OK.
Than, I have opened the project properties and under "Builders" section I have selected "import".
I have selected my program configuration from the list.
The error was: "Specified container for launch configuration does not exist."
Does anybody knows what this error mean?
That kind of error has been seen for instance with m2eclipse, and then described in the bug 247940
It seems a custom builder could not be defined on an imported project (as opposed to a project directly created in the eclipse workspace).
So if your .project and .classpath are defined in an external directory (external to the eclipse workspace), that may be the cause... and this is not yet addressed by eclipse3.5.