EasyEclipse for C and C++
Bare-bones Eclipse distro for experienced C and C++ developers who are new to Eclipse.
Download release 1.2.2:
(81MB)
(57MB)
(86MB)
Download release 1.3.1.1:
(101MB)
(81MB)
(107MB)
EasyEclipse for C and C++ is all you need to start developing C and C++ code with Eclipse.
There are currently 41 comments for this distribution. You can review them and add more here.
Composition
This distribution includes the following plugins:
Core components:
- Eclipse Platform - Shared platform services from Eclipse - Getting started.
- Java for Windows - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general C and C++ development:
- Eclipse C and C++ Development Tool - Create, compile, tests and debug and C and C++ applications and programs - Getting started.
- Eclox Doxygen frontend - Use the Doxygen code documentation framework in Eclipse - Getting started.
Version Control tools (CVS support was included in the Eclipse Platform until 1.2.2):
- Eclipse CVS client - Access and manage projects in CVS repositories within Eclipse - Getting started.
- Subclipse - Access and manage Subversion repositories within Eclipse - Getting started.
Miscellaneous:
- AnyEdit Tools - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", adds white spaces, tabs, and entities conversions, et cetera.
- Color Editor - Edit with syntax highlighting over 100+ file formats - Getting started.
Getting started
"Getting Started" documentation is available for the following included plugins:
- Eclipse Platform
- Eclipse C and C++ Development Tool
- Eclox Doxygen frontend
- Eclipse CVS client
- Subclipse
- Color Editor
Changelog
Changes in release 1.3.1.1:
- Patched: Fixed a configuration issue.
- Modified plugins:
- Upgraded to new version: Upgraded to Eclipse 3.3.1.
- Modified plugins:
- Eclipse Platform (upgraded)
- Eclipse C and C++ Development Tool (upgraded)
- Eclox Doxygen frontend (upgraded)
- Eclipse CVS client (upgraded)
- AnyEdit Tools (upgraded)
- Color Editor (upgraded)
- Upgraded to new version: Upgraded to Eclipse 3.3.0.
- Added plugin: Eclox Doxygen frontend
- Added plugin: Eclipse CVS client
- Modified plugins:
- Eclipse Platform (upgraded)
- Java for Windows (upgraded)
- Eclipse C and C++ Development Tool (upgraded)
- Subclipse (upgraded)
- Upgraded to new version: Upgraded to Eclipse 3.2.2.
- Changed composition: Removed Eclipse Tools that are not needed.
- Modified plugins:
- Eclipse Platform (upgraded)
- Java for Linux (upgraded)
- Eclipse C and C++ Development Tool (upgraded)
- Subclipse (upgraded)
- AnyEdit Tools (upgraded)
- Color Editor (upgraded)
- Modified plugins:
- Java for Windows (upgraded)
- Java for Linux (upgraded)
- Upgraded to new version: Upgraded to Eclipse 3.2.1.
- Modified plugins:
- Eclipse Platform (upgraded)
- Java for Windows (upgraded)
- Java for Linux (upgraded)
- Eclipse C and C++ Development Tool (upgraded)
- Subclipse (upgraded)
- AnyEdit Tools (upgraded)
- Color Editor (upgraded)
License
EasyEclipse is licensed under the terms of the Open Software License version 2.1.
Each third party plugin, software or content is licensed under its own copyright and/or license. See each plugin page for details
Does the distribution have no MinGW in it?
I can’t find any “make.exe”.
Do we need install MinGW ourself?
MinGW is not included. On Windows, you must install it. See the details on the C/C++ plugin page.
The Every Flavour Beans is the post that finally triggered me to want to build a combined CDT/MinGW package. I’ve started communicating with the EasyEclipse gang and we’ll see what we can get going.
I downloaded the windows installer and ran on a Vista machine. When I start the program, it fails with the following error:
!SESSION 2007-01-16 19:16:37.636 ———————————————–
eclipse.buildId=M20060921-0945
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 4 0 2007-01-16 19:16:45.753
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: no swt-win32-3235 in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123)
at org.eclipse.swt.internal.win32.OS.(OS.java:18)
at org.eclipse.swt.widgets.Display.(Display.java:125)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:433)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(IDEApplication.java:122)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:75)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
!ENTRY org.eclipse.osgi 2 0 2007-01-16 19:16:45.871
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.871
!MESSAGE Bundle update@plugins/org.eclipse.jem.workbench_1.2.1.v20060918_M.jar was not resolved.
!SUBENTRY 2 org.eclipse.jem.workbench 2 0 2007-01-16 19:16:45.871
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.871
!MESSAGE Bundle update@plugins/org.eclipse.jem.proxy_1.2.0.v20060918_M.jar was not resolved.
!SUBENTRY 2 org.eclipse.jem.proxy 2 0 2007-01-16 19:16:45.871
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.jem.proxy 2 0 2007-01-16 19:16:45.871
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.871
!MESSAGE Bundle update@plugins/org.eclipse.pde.core_3.2.1.v20060915-0800.jar was not resolved.
!SUBENTRY 2 org.eclipse.pde.core 2 0 2007-01-16 19:16:45.871
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.pde.core 2 0 2007-01-16 19:16:45.871
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.875
!MESSAGE Bundle update@plugins/org.eclipse.emf.codegen_2.2.1.v200609210005.jar was not resolved.
!SUBENTRY 2 org.eclipse.emf.codegen 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.emf.codegen 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.876
!MESSAGE Bundle update@plugins/org.eclipse.emf.codegen.ecore_2.2.1.v200609210005.jar was not resolved.
!SUBENTRY 2 org.eclipse.emf.codegen.ecore 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 2 org.eclipse.emf.codegen.ecore 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.launching_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.876
!MESSAGE Bundle update@plugins/org.eclipse.emf.importer.java_2.2.1.v200609210005.jar was not resolved.
!SUBENTRY 2 org.eclipse.emf.importer.java 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2007-01-16 19:16:45.876
!MESSAGE Bundle update@plugins/org.eclipse.jem.beaninfo_1.2.0.v20060918_M.jar was not resolved.
!SUBENTRY 2 org.eclipse.jem.beaninfo 2 0 2007-01-16 19:16:45.876
!MESSAGE Missing required bundle org.eclipse.jdt.core_[3.2.0,4.0.0).
Unfortunately the current version does not support Vista yet.
We are waiting for Eclipse core support for now. It is coming with the next release.
Hi, I downloaded EasyEclipse for C and C++ on my Ubuntu 6.06 AMD64 distro. Everything worked fine, until I tried to debug. When I open Run->Debug… it gave me the following error:
[Debugger]: The CPU is not supported by selected debugger.
Does this means that this distribution does not complete support amd64 machines?, or I’am doing something wrong?
At this time we only have support for Linux on X86 on X86_64. Could you enter a feature request?
http://sourceforge.net/tracker/?group_id=131065&atid=719798
I downloaded version 1.2.1.1. At first glance it looks great. But it seems there are some severe problems that prevent it from being used for real C++ projects.
The biggest problem is the inability to have a conceptual difference between files in the project, and files in the file system. For any kind of cross-platform development, there are going to be files (entire subdirectories and libraries!) that you don’t want to compile, because they are for a different platform, etc. But here I can’t do that without deleting them from the filesystem? It’s silly, there’s no good reason for it.
The second problem is the fact that the system seems to want to auto-compile things every time you make a change. C++ is a very slow language to compile sometimes (especially when using gcc) and compile effort is actually a resource that the developer needs to manage. In other words, I don’t want my computer grinding away trying to compile something unless I hit F7 (or whatever) and tell it to do that.
I look forward to further updates of eclipse because it would be great to have a useful IDE under Linux, and from what I’ve seen this is the closest one. But for now, I’m afraid it’s back to Makefiles and command-line everything for me…
After further playing with it…
I went and made makefiles for my app, and tried using it from a Standard Make project, but I can’t see any way to specify the location of the Makefile. The IDE just seems to assume that the Makefile is in the root directory, which is pretty much a showstopper. Seems like that would be easy to fix in a future version.
I found the setting to turn off the auto-compile, and that is much nicer. For C++ that should really be turned off by default.
I also found mention of the hack used to prevent the system from compiling all files. So I am going to have another go at a managed make project, and we’ll see what happens. I want to be able to use EasyEclipse…
I tried using EasyEclipse C/C++ to compile and execute a simple ANSI C program with ’scanf()’ and ‘printf()’ routines. It turns out that some unexpected results happens in the Eclipse Console, when in fact, the same program runs smoothly under “cygwin” X-Term after being compiled with gcc. Here is the simple C program I tried, after creating a “Managed Make C Project”:
#include
int main()
{
int integer1, integer2, sum;
printf(”Enter first integer:\n”);
scanf(”%d”, &integer1);
printf(”Enter second integer:\n”);
scanf(”%d”, &integer2);
sum = integer1 + integer2;
printf(”Sum is %d\n”, sum);
return 0;
}
The behaviour in the Console is that no “printf()” statements ever executed until after all the “scanf()” have been executed. Namely, I need to first type in the two integers before the “printf()” messages become visible and the sum is printed. This is certainly not the man-machine interaction intended in the program.
My question is this: Is the EasyEclipse C/C++ (or Eclipse’s CDT itself) programmed to handle the ANSI C’s basic input and output routines such ’scanf()’ and ‘printf()’ properly? For other ANSI C programs using only printf(), I observed that everything seems running smoothly.
That should be handled correctly. On my Mac is works OK :). However, CDT works better with minGW than with cygwin. That may be the cause of your trouble…
How can I open the Ant editor to hook into a C project’s configure/make build process? I can’t seem to be able to use ANT at all in this distribution?
Omar
Actually there is no ANT in the C++ dsitro. This is by design, as we removed anything about Java from that distro.
Now this is a first release, and if you think it should be added, add a feature request @ sf.net
In the meantime, to get ANT we would need to insall http://www.easyeclipse.org/site/plugins/eclipse-jdt.html which we do not ship yet as a separate plugin.
So short term there is no way out, unless you get the Java environment from Eclipse itself.
That would be the JDT Runtime Binary from http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/
Please enter a feature request here:
http://sourceforge.net/tracker/?group_id=131065&atid=719798
the JDT (Java Development Tools) is where Ant support is. It is relatively difficult to separate from the rest of the JDT, and I don’t want to put the all JDT into the C/C++ distro. However, we now ship the JDT as an installable plugin, so you just have to install it on your C++ distro. I think it’s a good enough fix…
The cdt debugger crashes under Mac OS X (ppc) 10.4.8, java.version=1.5.0_07, Eclipse 3.2.1
!ENTRY org.eclipse.cdt.debug.mi.core 4 150 2007-02-20 10:40:10.930
!MESSAGE Error creating session
!STACK 0
org.eclipse.cdt.debug.mi.core.MIException: Process Terminated
at org.eclipse.cdt.debug.mi.core.MISession.setup(MISession.java:226)
at org.eclipse.cdt.debug.mi.core.MISession.(MISession.java:198)
at org.eclipse.cdt.debug.mi.core.MIPlugin.createMISession0(MIPlugin.java:130)
at org.eclipse.cdt.debug.mi.core.MIPlugin.createSession(MIPlugin.java:456)
at org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createGDBSession(AbstractGDBCDIDebugger.java:109)
at org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createSession(AbstractGDBCDIDebugger.java:66)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugSession(LocalCDILaunchDelegate.java:307)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.createCDISession(LocalCDILaunchDelegate.java:432)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSession(LocalCDILaunchDelegate.java:138)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(LocalCDILaunchDelegate.java:105)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaunchDelegate.java:65)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:639)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:565)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:754)
at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
!SUBENTRY 1 org.eclipse.cdt.debug.mi.core 4 150 2007-02-20 10:40:10.933
!MESSAGE Process Terminated
!STACK 0
org.eclipse.cdt.debug.mi.core.MIException: Process Terminated
at org.eclipse.cdt.debug.mi.core.MISession.setup(MISession.java:226)
at org.eclipse.cdt.debug.mi.core.MISession.(MISession.java:198)
at org.eclipse.cdt.debug.mi.core.MIPlugin.createMISession0(MIPlugin.java:130)
at org.eclipse.cdt.debug.mi.core.MIPlugin.createSession(MIPlugin.java:456)
at org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createGDBSession(AbstractGDBCDIDebugger.java:109)
at org.eclipse.cdt.debug.mi.core.AbstractGDBCDIDebugger.createSession(AbstractGDBCDIDebugger.java:66)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugSession(LocalCDILaunchDelegate.java:307)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.createCDISession(LocalCDILaunchDelegate.java:432)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchLocalDebugSession(LocalCDILaunchDelegate.java:138)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launchDebugger(LocalCDILaunchDelegate.java:105)
at org.eclipse.cdt.launch.internal.LocalCDILaunchDelegate.launch(LocalCDILaunchDelegate.java:65)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:639)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:565)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:754)
at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:944)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Could you enter a bug for that?
I just tested it with 1.3 and didn’t have any issue using the “gdb Debugger” and “gdb/mi” configuration. the “gdbserver Debugger” didn’t work out-of-the box however. I suppose that this is fixed…
I have been trying to test compile and run the following program inside Eclipse’ CDT, but repeatedly received the following error message during the project build:
#include
main()
{
/* initializing variables in declaration */
int passes = 0, failures = 0, student = 1, result;
/* process 10 students; counter-controlled loop */
while (student
printf(”Raise tuition\n”);
return 0;
}
Error Message:
**** Build of configuration Debug for project Test-example ****
make -k all
make: Warning: File `objects.mk’ has modification time 1 s in the future
Building file: ../example.c
Invoking: GCC C Compiler
gcc -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF”example.d” -MT”example.d” -o”example.o” “../example.c”
Finished building: ../example.c
Building target: Test-example.exe
Invoking: GCC C Linker
gcc -o”Test-example.exe” ./example.o
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../libcygwin.a(libcmain.o):(.text+0xab): undefined reference to `_WinMain@16′
collect2: ld returned 1 exit status
make: *** [Test-example.exe] Error 1
make: Target `all’ not remade because of errors.
make: warning: Clock skew detected. Your build may be incomplete.
Build complete for project Test-example
Could someone help in spotting what is wrong with the CDT (”cygwin” has been installed to support gnu C compiling), or the program itself? Actually, the program runs under “cygwin” X-Terminal as expected.
It sounds like it is some trick cygwin is playing on you. Or have have been playing with the clock on your machine? You say that the programs runs allright?
Thanks! After creating another project and test running the same, I finally got the “build” complete and get the executable. And it works exactly as expected.
I do have the same problem. I have created already 3 times a new project with always the same mistake, as you mentioned above.
How did you solve it?
I believe that if you use mingw instead of cygwin, you won’t have this problem. See this comment. Please tell us if any issue !
I have tried both with mingw and cygwin.
It turned out that this is a bug, details are here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=173733
and here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=199219
Compiling with cygwin is somewhat shaky. Did you try mingw instead? it works like a charm.
Hello, could someone write tutorial for using easyeclipse and makeing some simple program. i do not know how to make exe file and to start apllication. Sorry for my bad english
it may works…check this…http://www.cs.umanitoba.ca/~eclipse/7-EclipseCDT.pdf
There are a few tutorials available on http://eclipse.org/cdt but we should definitely get something here. Your help would be welcomed
Actually, there’s a tutorial already !! check http://www.easyeclipse.org/site/plugins/eclipse-cdt.html#getting-started. Feedback is welcome.
When will CDT support real-time-error-check? This is very useful.
not sure what you mean…
Hi,
Is possible to compile QT based application on EasyEclipse?? Can anybody give a pointer that works for Windows version of the same..
thanks
Abhay
I keep having a problem with (I believe) MSYS. I have a P4/win XP system and I the ability for Eclipse to produce a “Binaries” file durring the build keeps disapearing. Deleating the programs and reinstalling them will fix my problem. But there must be a simpler way. I read a thread about a “-clean” option? and a system cache file?, but I can’t seem to find any good info, to help.
Thanks
I have read a related thread under the topic of “EasyEclipse Expert Java” distro with regard to the libc error on RHEL/CENTOS 5. I am experiencing the same error on RHEL 5.3 Server. I have the latest xulrunner, xulrunner-devel and firefox-3.0.7 rpms installed. I have tried Antoine’s latest suggestion that seemed to work for him and was unsuccessful.
I get a number of different errors on start-up of eclipse at the same point in the initialization process, but only one error each attempt:
# C [libc.so.6+0x710a5] memcpy+0×15
# C [libxul.so+0xd05900]
# C [UTF-16.so+0x88d] gconv+0×1fd
References:
2009-02-19 11:36:00: Antoine on EasyEclipse Expert Java
2009-02-19 09:31:01: Antoine on EasyEclipse Expert Java
2009-02-19 08:51:06: Antoine on EasyEclipse Expert Java