- Apr 23, 2020
-
-
Nadeem Shehzad authored
-
- Apr 22, 2020
-
-
Martin Christoph Hierholzer authored
-
- Apr 09, 2020
-
-
Christoph Kampmeyer authored
- Clean up serverTestDataMatching - Fix missing include in test
-
- Apr 07, 2020
-
-
Christoph Kampmeyer authored
- Fix default setting for imported locations (solves #39) - Test for imported scalar properties
-
- Apr 01, 2020
-
-
Automated MSK Jenkins User authored
-
- Mar 13, 2020
-
-
Automated MSK Jenkins User authored
-
- Mar 06, 2020
-
- Mar 05, 2020
-
-
Martin Christoph Hierholzer authored
- was confusing milliseconds and microseconds for the archiver - was not setting the global time stamp
-
- Mar 02, 2020
-
-
Jens Georg authored
Since Doocs 20.1 this is thrown if the name of the property exceeds 64 characters
-
- Feb 09, 2020
-
-
Automated MSK Jenkins User authored
-
- Feb 05, 2020
-
-
Martin Christoph Hierholzer authored
This is a new requirement from ApplicationCore.
- Jan 31, 2020
-
-
Automated MSK Jenkins User authored
-
- Jan 28, 2020
-
-
Martin Killenberg authored
-
Automated MSK Jenkins User authored
- Jan 27, 2020
-
-
Martin Killenberg authored
-
vargheseg authored
Extra space at the end of a property name has been removed in the latest version of doocs. These tests were modified to work with this change: - testCSAdapterEqFct - testDoocsPVFactory
- Jan 08, 2020
-
-
Martin Killenberg authored
add two more ignores related to eclipse projects.
-
zenker authored
-
- Dec 11, 2019
-
- Dec 09, 2019
-
-
Martin Killenberg authored
By default, the timestamp that is attached to a variable is the global time stamp, which is only set updated by update() in the adapter, which is not used otherwise. The adapter already was setting it for the time stamp that is attached to the variable itself, but not for the time stamp that used for archiving. This has been fixed. Now the time stamps in the Doocs histories are set correctly. To test it run example2 of ApplicationCore, togehter with the oven_sim simulation and watch Oven.heatingCurrent.HIST
-
- Oct 14, 2019
-
-
Jens Georg authored
THis is necessary for newer Boost (1.71) which puts the exported targets in Boost_LIBRARIES. If we export that verbatim it causes link issues on projects using the config scripts from Make
-
- Sep 27, 2019
-
-
Christoph Kampmeyer authored
-
- Sep 25, 2019
-
-
Jens Georg authored
This reverts commit e7294d81. This does not exist on xenial yet
-
- Sep 24, 2019
-
-
Jens Georg authored
find_package is for use inside the *Config.cmake files
-
Jens Georg authored
To add public dependencies to the generated config, use e.g. list(APPEND ${PROJECT_NAME}_PUBLIC_DEPENDENCIES "Boost COMPONENTS system thread chrono")
-
- Sep 11, 2019
-
-
Martin Christoph Hierholzer authored
-
- Aug 15, 2019
-
- Jul 10, 2019
-
-
Jens Georg authored
-
- Jun 27, 2019
-
-
Martin Christoph Hierholzer authored
output warning if data is thrown away due to failed consistency matching between macro pulse number and actual data
-
Martin Christoph Hierholzer authored
- Jun 26, 2019
-
-
Martin Christoph Hierholzer authored
-
Martin Christoph Hierholzer authored
-
Martin Killenberg authored
remved the library without path from the _LIBRARIES. It is added with path by the config file anyway, which makes linking easiser because you don't need the link path variable.
-
- Jun 24, 2019
-
-
Jens Georg authored