Please use our GitHub Issue Tracker to report bugs and feature requests .
No. As of version 1.11.1, Cevelop is a 64-bit-only application. This is because the underlying Eclipse Platform dropped 32-bit support.
This is usually caused by an outdated Java version or because it is a 32-bit version of Java. Cevelop requires 64-bit Java 8 to run.
Here are some links to get you started:
We pronounce it as «see-vel-op», just like «see-plus-plus».
See our license page.
Please contact us with your requirements. We might find an agreement. Financial support is always appreciated, but we can't yet accept micropayments.
Major parts of Cevelop are Open Source as Eclipse CDT to which we actively contribute, especially in the area of the C++ parser and refactoring infrastructure.
However, many of the Cevelop-specific extensions have been created with Swiss tax payer's money and we are obliged to make revenue within our university to sustain our workforce. Funding can result in more and better features of Cevelop and other tools we develop. No funding might mean that we can not sustain it, and we do not want vendors selling Eclipse CDT-based IDEs to benefit from our work, without even recognizing it was done by us. However, with financial compensation we are happy to provide corresponding licenses and support, as long as we can continue to use Cevelop for our students. Please contact us.
Cevelop is based on the Eclipse C/C++ Development Tools, which handles the detection of the toolchain. If you've installed MinGW and Cevelop doesn't find it, please see the Eclipse FAQ.
One of the trickiest tasks to get right when setting up a project in Cevelop is the include paths. This Eclipse newsletter discusses the several options and configuration dialogs.
To suppress a message, you can add a line comment that specifies the message to suppress. For example:
char* name = "Cevelop"; // @suppress("Use std::string instead of C-Strings.")
In the future, we plan to have a quick-fix that adds the correct suppression message for you, but at the moment, you'll need to look it up in the preferences:
The name of the problem is used in the suppression comment. You can also deactive an analysis completely to silence it. Customize Selected... gives you further configuration options for the analysis. For example, you can change the suppression pattern.
You can edit the cevelop.sh script to force Cevelop to use GTK2.
To include boost headers you first have to download the newest header files from the official boost homepage and unpack them to the location of your choice. In Cevelop, right-click on your project and choose Properties. In C/C++ General → Paths and Symbols you can include the boost directory as follows:
Click Apply and close the dialogue. You are now able to include boost headers in your project files. Note that this does not only work for boost, but any header files you would like to include in your project.
If you are working on large projects using Cevelop, you may need to increase the maximum Java heap size in order to avoid Out-of-Memory exceptions.
You can increase this size by changing the following line in the cevelop.ini file:
-Xmx2048m
For example, if you want to increase the maximum Java heap size from the default of 2048MB to twice that size, you can change this line to
-Xmx4096m. On Windows and Linux the cevelop.ini file is located at the root of the Cevelop folder and on macOS it can be found in the Cevelop.app/Contents/Eclipse folder.
CMake is currently not natively supported by Cevelop. There are multiple ways to import your CMake projects into Cevelop. Please follow one of the following guides.
Using cmake inside the source directory:
cmake inside your projects root directory and pass -G"Unix Makefiles" as an additional option.Using cmake outside of the source directory:
cmake in a folder outside of your projects source directory and pass -G"Eclipse CDT4 - Unix Makefiles" and -DCMAKE_CXX_FLAGS "-std=c++XX" to the command. Replace the XX with the standard you wish to use. This ensures that the indexer knows the correct C++ Standard version for your project.cmake in as the root directory.After either of these steps the project can be run and built directly from inside Cevelop.
There are two ways you can do this in Cevelop. If the library is a separate Cevelop project in the same workspace, you can do the following:
The end result should look like this:
If you instead want to add the library and its header files directly to the executable project, you can do that as well. However, this means that you need to manually specify the library path, library name, etc:
