Skip to content

Commit

Permalink
[ISSUE #203] Compilation of the plugin fails with CMake 3.28.1
Browse files Browse the repository at this point in the history
This patch extends the documentation of the DLT Message Analyzer. A
clarification is added regarding the issue #203.

Signed-off-by: Vladyslav Goncharuk <[email protected]>
  • Loading branch information
Vladyslav Goncharuk committed Jul 7, 2024
1 parent 89a8df1 commit f5497a0
Showing 1 changed file with 18 additions and 0 deletions.
18 changes: 18 additions & 0 deletions md/installation_guide/installation_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ Table of contents
- [Build dependencies](#build-dependencies)
- [Build settings](#build-settings)
- [dlt-viewer-docker](#dlt-viewer-docker)
- [Troubleshooting](#troubleshooting)
- [CMake 3.28.1](#cmake-3281)

----

Expand Down Expand Up @@ -231,4 +233,20 @@ The usage is quite simple:
----
## Troubleshooting
### CMake 3.28.1
It was identified that with version 3.28.1 of the CMake tool, you will get the following error during the DLT Message Analyzer build:
> make[2]: *** No rule to make target 'plugin/DLT-Message-Analyzer/dltmessageanalyzerplugin/src/antlr4_runtime/src/antlr4_runtime/runtime/Cpp/dist/libantlr4-runtime.a', needed by 'plugin/DLT-Message-Analyzer/dltmessageanalyzerplugin/src/CMakeFiles/antlr4_PCRE_static_autogen_timestamp_deps'. Stop. make[1]: *** [CMakeFiles/Makefile2:1716: plugin/DLT-Message-Analyzer/dltmessageanalyzerplugin/src/CMakeFiles/antlr4_PCRE_static_autogen_timestamp_deps.dir/all] Error 2 make: *** [Makefile:156: all] Error 2
It is likely caused by the bug in that specific version of CMake, combined with the old-style CMake scripting used by the Antlr4 C++ runtime.
As a reliable solution, please switch to the other CMake version. E.g., 3.22.1 and 3.29.6 worked just fine.
You can find more details regarding this issue [here](https://github.com/svlad-90/DLT-Message-Analyzer/issues/203).
----
[**Go to the previous page**](../../README.md)

0 comments on commit f5497a0

Please sign in to comment.