Conversation
| @@ -1,7 +1,9 @@ | |||
| cmake_minimum_required(VERSION 3.12) | |||
| cmake_minimum_required(VERSION 3.20) | |||
There was a problem hiding this comment.
CMake 3.20 required for the presets
There was a problem hiding this comment.
I think this is aligned and serve as a example towards showing up a time-series of events.
There was a problem hiding this comment.
I meged it in my fork mm-s/DebugVision.git
|
I think this is aligned and serve as a example towards showing up a time-series of events. |
Could not find a package configuration file provided by "QT" with any of
the following names:
Qt6Config.cmake
...Cmake should write an include file called config.h defining the macro writing 0 or 1 depending on whether qt is available in the system or not, or --without-qt is selected At most CMake shall report that the system is configured without Qt, but currently it fails with error |
It can, but I configured the search for Qt to be |
./scripts/install_recent_cmake.shapt-get install -qq ninja-build qt5-default libqt5x11extras5-devtoolsdir rather than asrcdir, but why not*.log,log*.txt)IMO, a key element in such an application is the text viewer. here I use a QTextEdit, but for a real log viewer app this class is not powerful enough, in terms of capacity to display huge log files, line numbers, customize line colors, etc... So I think a special widget has to be developed for that purpose. And I think it will apply to any GUI toolkit being used. And it can be a tricky task depending on the toolkit being used. I managed to quickly do a skeleton with Qt, with very good performances. But failed with Dear ImGui. I think OpenGL based toolkits are not well suited to build such text intensive widgets. At least that's the feeling I got from my experiments.