- Restore compatibility with CDT 11.4/Eclipse 2023-12.
- Fix #197: Run builder on empty delta to react on when the active configuration changes.
- Disallow to install it on CDT 11.4 (2023-12) since it is not compatible with CDT 11.4 and newer.
- Ensure project relative path are below project directory (no '..').
- Fix project creation over existing cmake4eclipse project of versions < 4.x.
- Added a context menu to edit build targets.
- Fix #182: "Warn about uninitialized values" passes wrong cli-option to cmake.
- Fix #183: "--warn-unused-vars" has been removed in CMake 3.19 and above.
- Fix #180: Allow adding arbitrary cmake command line arguments
- Requires Java 17 as a prerequisite.
- Removed the deprecated CMAKE_EXPORT_COMPILE_COMMANDS language setting providers. Their code has long been integrated into CDT. As a replacement, users should switch to the CMake Compilation DB parser which is based on the code in CDT.
- Removed the deprecated CMake Builder (deprecated). It has been kept for compatibility with cmake4eclipse 2.x and is superseded by the CMake Builder.
- Replaced the cmake error parser with the parser coming with CDT. This does not affect end-users but helps to reduce maintenance effort.
- Added a new cmake4eclipse project creation wizard. Projects created through that wizard are still based on the managed build system (MBS) but do not show all the project property pages inherited from MBS that confuse end-users. Many of those MBS properties have no meaning when build-scripts are created by cmake (e.g. build artifact extension).
- Requires CDT 11.0 as a prerequisite.
- Fix #176: Support multiple source locations.
- Fix NoSuchFileException '_build/Debug/_deps'
- Fix #174: "Resource '/home' does not exist."
- Fix 'process not terminated' exception
- Closed #172: docker build and additional include paths: eclipse doesn't find the includes
- Use java.nio.file.Paths instead of java.io.File
- FIX: Also remove cache files for external projects that were downloaded by cmake's FetchContent call.
- Do not update index in projects that were closed.
- Honor workbench setting for builtins-detection console.
- Closed #171: JSON Compilation Database Parser does not recognize built-ins.
- Closed #167: bison from <MSYS2_ROOT>\usr\bin fails when run for projects targeting mingw32 on windows.
- Add support to export and import Cmake4eclipse workbench preferences.
- Closed #164: NPE in BuildToolKitUtil.getEffectiveCMakeGenerator() when workspace preferences for cmake4eclipse has never been saved.
- Closed #157: For CDT indexer support, switch to the compilation database parser coming with CDT.
- Closed #158: Move machine specific settings from project to workbench preferences.
Compatibility Note: Eclipse projects creating with earlier version of cmake4eclipse should continue to work but
users are strongly recommended to switch project properties to use the new
CMake driventool chain.
- CDT v 10.5 or newer and Eclipse v 2021-12 or newer
- Java 11 or newer
- Closed #147: Retain order of compiler-built-in include directories.
- Take changes to *.cmake files into account when determining whether to re-run cmake.
- Closed #145: Add support for clang
--targetoption. (Thanks to Ghaith Hachem).
- Closed #138: Recognize GCC/clang -include and -imacros compiler flags.
- Fix: Missing bundles for ARM, HPE-nonstop and Intel support in the
cmake4eclipse Extrassection in the repository. - Raised severity level to WARNING for markers related to indexer support.
- Changed license to EPL 2.0
- Syntax highlighting support for NVidia and Microsoft compilers are no longer supported out-of-the box. Support is now handled through separate plug-ins. End users will have to install these separate plug-ins to get support for the compilers.
- Closed #128: GNU C++ CMAKE_EXPORT_COMPILE_COMMANDS Compiler Built-ins empty.
- Additional unit tests for compiler detection participants.
- Fix 127: Installation impossible due to dependency on bundle org.eclipse.ui.trace.
- Fix: Make builtins.DetectorConsole visible again (regression).
- Added a tool-chain
CMake driventhat will configure the proper builder when selected to make project configuration easier. - Added a project type
CMake drivento the CDTNew C ProjectandNew C+ Projectwizard to ease in project creation. - Deprecated
CMake Builder (GNU Make). Existing projects will still use that builder but it cannot be selected in the UI any longer. - Added an extension point
lspDetectionParticipant, allowing 3rd-party compiler vendors to integrate a compiler for improved syntax highlighting in the CDT's C/C++ editors by simply providing an Eclipse plug-in. The CMAKE_EXPORT_COMPILE_COMMANDS Parsers of this plug.in will pick-up thelspDetectionParticipantextensions to detect preprocessor macros and include directories. - Syntax highlighting support for ARM.com and Intel compilers are no longer supported out-of-the box. Support is now
handled through separate plug-ins that provide implementations of the
lspDetectionParticipantextension point.
End users will have to install these separate plug-ins to get support for the compilers. - Closed #119: Support for HPE non-stop compilers. Note this has not been tested yet.
- CMAKE_EXPORT_COMPILE_COMMANDS Parser: Allow compiler paths in quotes.
- Close #122: CMAKE_EXPORT_COMPILE_COMMANDS Parser does not recognize /some/path/arm-none-eabi-c++.
- Close #117: CMAKE_EXPORT_COMPILE_COMMANDS Parser: support ARM compiler toolchain.
- Make windows short file name expansion more robust.
- Add tracing support.
- make short file name expansion on windows more robust, log file-name on error.
- fix IndexOutOfBoundsException during built-ins detection.
- Fix #116: CMake errors are not detected if a project is re-build.
- Fix #96 and #108: Pass compiler flags that affect compiler built-ins detection to the compiler when detecting built-ins.
- Fix #112: cmake cache entries only saved for one configuration.
- Reviewed online help.
- Fix #101: ParserDetecter for MSVC cannot distinguish between C and C++.
- Fix #95: Provide programmatic access to CMake configuration.
- Fix UnsupportedOperationException at CompileCommandsJsonParser$TimestampedLanguageSettingsStorage.addBuiltinsDetector().
- Fix NPE when build is running in container.
- Fix RuntimeException: "Ignored reentrant call while viewer is busy" in settings providers on workbench startup.
- Fix #94: CMAKE_EXPORT_COMPILE_COMMANDS parser fails to parse inline-command-files @<<...<<
- Fix #97: Adjust documentation to newer CDT versions.
- CMAKE_EXPORT_COMPILE_COMMANDS Built-ins Parser: run detection in container, if build runs in container.
- UI/doc: Use Cmake4eclipse instead of just CMake to avoid confusion with CDT`s new cmake support.
- Add optional console view for compiler built-ins detection (#96).
- Fix: CMAKE_EXPORT_COMPILE_COMMANDS * Parser settings were not persisted for projects.
- Fix #99: CMAKE_EXPORT_COMPILE_COMMANDS Parser for MSVC does not cover "-" flags.
- Change related to #73 (CMake Error Parser): Deleted the old parser (which was based on CDT output handling and gave poor results) and re-wrote it from scratch. Note that the new parser does not claim to detect any cmake message; more input from the community is required to detect more messages.
- Removed deprecated CMake Build Output Parser.
- Fixed #86: Parsing compile_commands.json creates duplicate entries.
- Fixed #85: Poor workbench startup performance due to doing a IIndexManger.reindex().
- Fixed #84: CMAKE_EXPORT_COMPILE_COMMANDS Parser no longer detects macros specified on a command-line.
- Fixed #79: CMAKE_EXPORT_COMPILE_COMMANDS Parser does not detect compiler-built-in macros and include paths.
- Builtins-detector get no longer started in non-existing CWD.
- Plugin now requires Java 8, Eclipse 4.5 (mars) and CDT 8.7 to run.
- Reworked documentation (a little).
- Fixed #79: CMAKE_EXPORT_COMPILE_COMMANDS Parser does not detect compiler-built-in macros and include paths. (Forget CDT's GCC-builtin-specs-detector:-)
- Fixed #78: NPE when running builder 'CDT Builder' on project.
- Fixed #80: Custom build command is not used verbatim.
- Eliminate duplicate mnemonics in UI.
- Build in docker container: Fix NPE occurring in CDT 9.4+ with docker build launcher.
- Build in docker container: let CDT copy header files back when building in a docker container.
- Fixed #52: Allow to run parallel builds.
- Fail the build if build tool name cannot be determined from CMakeCache.txt.
- Fixed #65: Recognize nvcc as a CUDA compiler and integrate with the Nsight Eclipse Plugins.
- Merge pull request #67 from @havogt: Allow -isystem without whitespace.
- Fixed #68: Allow to parse -isystem= (nvcc compiler).
- Fixed #64: Project is fully reindexed after each build.
- Enhancement: Improve diagnostic messages during build-script generation.
- Enhancement #23: Handle CDT variables instead of just eclipse core variables.
- Enhancement #58: CMAKE_EXPORT_COMPILE_COMMANDS Parser now evaluates compiler options passed in a "response file".
- Enhancement #52: Make 'CMake Make Builder' GNU-make specific and allow to build in parallel. Builder renamed to 'CMake Builder (GNU Make)'
- Enhancement #54: Support variable expansion in build output location.
- Fixed #55: NPE if project is of plain make-nature (no managed build).
- Fixed #51: No error message in build log, when cmake executable could not be found.
- Revised online documentation.
- Enhancement #57: Add workaround for relative include paths produced by cmake`s ninja generator.
- Enhancement #29: make the Output directory configurable
- Fixed #48 NPE in project configuration when OK button is clicked
- Enhancement #46 Populate CMake cache entries from a file
- Enhancement: Added mnemonics to UI
- Fixed: "ResourceException: The resource tree is locked for modifications" when opening project.
- Fixed #38: Build occurs in eclipse install directory.
- fixed #43 CMAKE_EXPORT_COMPILE_COMMANDS Parser should support different versions of compilers
- Fixed #44: CMAKE_EXPORT_COMPILE_COMMANDS Parser fails for command paths using a forward slash
- CMAKE_EXPORT_COMPILE_COMMANDS Parser show problems in Problems View instead of writing them to the application log file
- Fixed #36: Variable substitution for CMake executable
- Added documentation on project builders
- Fixed #41: CMAKE_EXPORT_COMPILE_COMMANDS Parser doesn't work if compiler command doesn't contain full path
- Fixed #39: Enabling build output parser does not pass necessary arguments to cmake
- Closed #26: CMakeFiles, cache and others generated into wrong directory
- Closed #31: CMAKE_EXPORT_COMPILE_COMMANDS Parser fails if compiler executable has a MSDOS "Short path" name. Thanks to @nolange for reporting and testing under windows
- Requires Java 7 or newer
CDT v 8.7 or newer and Eclipse v 4.5 (Mars) or newer
Java 7 or newer
- Closed #28: CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- Closed #24: CMake dialog box does not save all modified configs.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- Closed #20: CMAKE_EXPORT_COMPILE_COMMANDS Parser treats clang++ as a C compiler.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- Closed #17: CMAKE_EXPORT_COMPILE_COMMANDS parser doesn't recognize g++ as a C++ compiler.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- Closed #16: The CMAKE_EXPORT_COMPILE_COMMANDS parser now knows about GCC cross compilers for C and C++ if the compiler executable follows the naming convention of
<target_triplet>-gccor<target_triplet>-g++.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- CMAKE_EXPORT_COMPILE_COMMANDS Parser triggers UI update to show newly detected include paths in project explorer view.
- Closed #14: Pass variables given in C++ Build->Environment to the cmake process.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
- Closes #9: Improve support for code-completion and symbol browsing in CDT source editors.
- Closes #10: Can't install version 1.4.0 in eclipse mars.2 release 4.5.2
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
These releases are made available as a zipped p2 repository. To install, use the "Install New Software..." menu and paste the appropriate repository URL from below into the "Work with" input field.
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
These can be found at https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/ .
Do not forget to add the trailing !/ to the repository URL!
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-1.3.2.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-1.3.1.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-1.3.0.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-1.1.0.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-1.0.0.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher
jar:https://googledrive.com/host/0B-QU1Qnto3huZUZ0QUdxM01pR0U/cmake4eclipsecdt-Update-0.1.0-SNAPSHOT.zip!/
CDT v 8.1.0 or higher and Eclipse v 3.8.0 (Juno) or higher