Allow 100% raw CMake to be used in a TriBITS-compliant package (#582)

[bartlettroscoe]

Addresses:

• 582

Description

This PR provides the changes to TriBITS and the TribitsExampleProject2 project to allow 100% raw CMake (with no TriBITS commands or functionality at all) to be used to define a TriBITS-compliant package. Such a TriBITS package should a a valid [TriBITS-compliant internal package] (https://tribitspub.github.io/TriBITS/users_guide/index.html#tribits-compliant-internal-packages) and produce a TriBITS-compliant external package.

Tasks

• [x] Set up faling test to configure TribitsExampleProject2 Package1 using raw CMake and no calls to TriBITS at all
• [x] Update TriBITS and TribitsExampleProject2/packages/package1/CMakeLists.txt to work with all raw CMake
• [x] Add/extend all tests to use raw CMake build for Package1 inside TriBITS project build in all test cases (and add regexes that can verify this)
• [x] Update Package1 raw CMake build to allow using TriBITS test functions under a TriBITS project
• [x] Update Package1 raw CMake build to allow using tribits_add_test() in stand-alone raw CMake project
  • [x] Refactor test support TriBITS code into tribits/core/testing_support/ and modules that can be directly included without setting CMAKE_MODULE_PATH?
• [ ] Update TriBITS to use TRIBITS_PROJECT_NAME, ${TRIBITS_PROJECT_NAME}_SOURCE_DIR and ${TRIPTS_PROJECT_NAME}_BINARY_DIR instead of PROJECT_NAME, PROJECT_SOURCE_DIR and PROJECT_BINARY_DIR, respectively, and make all tests pass (to support use cases like the Sierra prototype CMake build that is including a TriBITS project under a non-TriBITS project using add_subdirectory() where TRIBITS_PROJECT_NAME != CMAKE_PROJECT_NAME or PROJECT_NAME) Not needed for these use cases but will be needed if a TriBITS project is pulled into a larger CMake base project using add_subdirectory().

[bartlettroscoe]

Hello @KyleFromKitware, if you have some time, can you please review this PR? It is likely better to review it commit-by-commit than all-at-once.

[bartlettroscoe]

@KyleFromKitware, I think this is ready to merge as it has resolved all of your comments. Can you approve the PR if it looks good to you?

[bartlettroscoe]

Hello @KyleFromKitware, can you please do a post-merge review of the generated documentation at:

• https://tribitspub.github.io/TriBITS/users_guide/index.html#how-to-implement-a-tribits-compliant-internal-package-using-raw-cmake
• https://tribitspub.github.io/TriBITS/users_guide/index.html#how-to-implement-a-tribits-compliant-external-package-using-raw-cmake
• https://tribitspub.github.io/TriBITS/users_guide/index.html#how-to-use-tribits-testing-support-in-non-tribits-project
• https://tribitspub.github.io/TriBITS/users_guide/index.html#using-tribits-add-advanced-test-in-non-tribits-cmake-projects

?

This refers to the raw and CMake build system under:

• https://github.com/TriBITSPub/TriBITS/tree/master/tribits/examples/TribitsExampleProject2/packages/package1