Skip to content

Conversation

@burrima
Copy link

@burrima burrima commented Jan 26, 2020

Necessary since it conflicts with internal cmake/ctest mechanisms (see
https://cmake.org/cmake/help/latest/command/enable_testing.html).

Thank you @cryptomilk for pointing this out!

Signed-off-by: Martin Burri [email protected]

Necessary since it conflicts with internal cmake/ctest mechanisms (see
https://cmake.org/cmake/help/latest/command/enable_testing.html).

Thank you @cryptomilk for pointing this out!

Signed-off-by: Martin Burri <[email protected]>
@burrima burrima requested a review from LebedevRI as a code owner January 26, 2020 09:50
Copy link
Member

@LebedevRI LebedevRI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please can you explain how it conflicts?
The option is named as such precisely because there is BUILD_TESTING option.

@burrima
Copy link
Author

burrima commented Jan 26, 2020

Related to this pull request in darktable: darktable-org/darktable#4154
The statement from @cryptomilk was that rawspeed is setting the option BUILD_TESTING to Off which would disable it globally in darktable.

@LebedevRI
Copy link
Member

Setting it where?

@burrima
Copy link
Author

burrima commented Jan 26, 2020

Ok, I will talk to @cryptomilk first when he is back from the devconf.cz - I understand too little of cmake to give you a good explanation. Please stay tuned.

@cryptomilk
Copy link
Contributor

You can close this, it is a non-issue :-)

@LebedevRI
Copy link
Member

As discussed in darktable-org/darktable#4154 (comment)

@LebedevRI LebedevRI closed this Jan 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants