Closed OPNA2608 closed 2 weeks ago
This change will be accepted.
Thanks too much everyone and github also
On Thu, 17 Oct 2024, 04:44 Aliaksei Levin, @.***> wrote:
Merged #3084 https://github.com/tdlib/td/pull/3084 into master.
— Reply to this email directly, view it on GitHub https://github.com/tdlib/td/pull/3084#event-14689833266, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJ4PV45SSTPR6BUWTXYSJBDZ33M4TAVCNFSM6AAAAABPZZOP76VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGY4DSOBTGMZDMNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
By the way, if you include projects via add_subdirectory
there are no issues, because BUILD_TESTING must be used explicitly to have any effect. This isn't a built-in option like BUILD_SHARED_LIBS, CMAKE_INSTALL_PREFIX, or CMAKE_BUILD_TYPE, which have implicit effect on all projects.
https://cmake.org/cmake/help/v3.0/module/CTest.html explains that including the
CTest
module and using the createdBUILD_TESTING
option allows users to opt out of creating tests when testing isn't desired.This is what I would usually submit to projects, where using it via
add_subdirectory()
from another project is not a consideration. SinceBUILD_TESTING
is a cache variable, is this a problem again? So maybe just…without including
CTest
(since that's what defines theoption()
)? Though this would default to the tests not being built, while using theoption()
would preserve current behaviour…