Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change OmrTracegen message from a warning to a status #3652

Merged
merged 1 commit into from
Mar 9, 2019

Conversation

youngar
Copy link
Contributor

@youngar youngar commented Mar 8, 2019

Old warning message was quite verbose, and not a real warning. By
changing the message to status the output is less alarming.

From:

CMake Warning at cmake/modules/OmrTracegen.cmake:32 (message):
  OMR: No trace root has been set.  Defaulting to
  '/home/aryoung/wsp/omr/build'
Call Stack (most recent call first):
  CMakeLists.txt:43 (include)

To:

-- OMR: No trace root has been set. Defaulting to '/home/aryoung/wsp/omr/build'

Signed-off-by: Andrew Young youngar17@gmail.com

Old warning message was quite verbose, and not a real warning.  By
changing the message to status the output is less alarming.

From:
```
CMake Warning at cmake/modules/OmrTracegen.cmake:32 (message):
  OMR: No trace root has been set.  Defaulting to
  '/home/aryoung/wsp/omr/build'
Call Stack (most recent call first):
  CMakeLists.txt:43 (include)
```

To:
```
-- OMR: No trace root has been set. Defaulting to '/home/aryoung/wsp/omr/build'
```

Signed-off-by: Andrew Young <youngar17@gmail.com>
@youngar youngar added the cmake label Mar 8, 2019
@youngar youngar requested a review from charliegracie as a code owner March 8, 2019 16:22
@charliegracie
Copy link
Contributor

The AppVeyor build uses CMake so no further testing is required

@charliegracie charliegracie self-assigned this Mar 9, 2019
@charliegracie charliegracie merged commit 00a1312 into eclipse-omr:master Mar 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants