In order to increase the level of the support of our users, we need to start to prepare releases with automatically deliverable artifacts.
Currently, we need the following builds to be supported:
Windows build for msvc-2013 & Qt 5.5.1 for version 2.19 of the dlt-viewer ( to support one of the actual projects )
Windows build for msvc-2013 & Qt 5.5.1 for version 2.20 of the dlt-viewer ( to support one of the actual projects )
Windows build for msvc-2019 & Qt 5.15.0 for version 2.19 of the dlt-viewer
Windows build for msvc-2019 & Qt 5.15.0 for version 2.20 of the dlt-viewer
Linux build
For Windows, the artifact should be an archive with dlt-viewer + DLT-Message-Analyzer plugin inside.
For Linux, the artifact should be an archive with dlt-viewer's + DLT-Message-Analyzer's source code inside, ready for being compiled with CMake.
For Linux, build is not actually needed, as only the source code is part of the delivery. Still, the corresponding build should compile the code, in order to prevent the delivery of non-compilable source code.
In order to increase the level of the support of our users, we need to start to prepare releases with automatically deliverable artifacts.
Currently, we need the following builds to be supported:
For Windows, the artifact should be an archive with dlt-viewer + DLT-Message-Analyzer plugin inside. For Linux, the artifact should be an archive with dlt-viewer's + DLT-Message-Analyzer's source code inside, ready for being compiled with CMake.
For Linux, build is not actually needed, as only the source code is part of the delivery. Still, the corresponding build should compile the code, in order to prevent the delivery of non-compilable source code.