- Jan 05, 2017
-
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
- Jun 07, 2016
-
-
Michael Grünewald authored
Close #215
-
Michael Grünewald authored
-
- Jun 06, 2016
-
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
Closes #160.
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
- Jun 05, 2016
-
-
Michael Grünewald authored
-
- Jun 04, 2016
-
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
-
Michael Grünewald authored
- Arrange report on failed test to display hashes of failed tests. - Connect help to UI. - Remove debugging function entry point
-
Michael Grünewald authored
There is one subtle point to consider when crafting a MAKEOBJDIR variable using the CONFIGURATION and ARCHITECTURE variable. The point is that the .OBJDIR directory is made before everything else, which means that variables CONFIGURATIONDIR and ARCHITECTUREDIR deduced from the two others are *not* available at the time where .OBJDIR is computed. This leads to a odd and hard to diagnose behaviour. Instead of using CONFIGURATIONDIR and ARCHITECTUREDIR one can use ${CONFIGURATION:C@^.@/&@} and ${ARCHITECTURE:C@^.@/&@} in the definition of MAKEOBJDIR. -
Michael Grünewald authored
-
Michael Grünewald authored
-
- May 27, 2016
-
-
Michael Grünewald authored
-
Michael Grünewald authored
-
- May 18, 2016
-
-
Michael Grünewald authored
-
- Jan 17, 2016
-
-
Michael Grünewald authored
-