Project

General

Profile

Actions

Development #1387

closed

Set PROFILE as default build option

Added by Volker Friese almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
10/08/2019
Due date:
10/11/2019
% Done:

100%

Estimated time:
1.00 h
Spent time:

Description

After fixing the compiler warnings (see #1353), the default build type should be PROFILE in all tests and in the local builds, such that warnings can be detected before submitting to SVN.


Related issues

Follows CbmRoot - Development #1353: Code cleanup for OCT19ClosedVolker Friese09/10/201910/07/2019

Actions
Actions #1

Updated by Volker Friese almost 3 years ago

  • Due date set to 10/08/2019
  • Start date changed from 09/18/2019 to 10/08/2019
  • Follows Development #1353: Code cleanup for OCT19 added
Actions #2

Updated by Volker Friese almost 3 years ago

  • Due date changed from 10/08/2019 to 10/11/2019
Actions #3

Updated by Florian Uhlig almost 3 years ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Florian Uhlig to Volker Friese
  • % Done changed from 0 to 100

A new build type called FullWarnings was implemented which sets the warning compile flags as used in build type Profile. I did not use the build type Profile because this is especially meant to compile and test code for coverage analysis.

If no build type is defined by passing the command line option -DCMAKE_BUILD_TYPE the new build type FullWarnings is used as default. The new build type is also used for the continuous builds. So from now on warnings should show up immediately when the code is committed to the repository.

Actions #4

Updated by Volker Friese over 2 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF