Generated file:

set(BEMAN_EXEMPLAR_VERSION 0.1.0)


####### Expanded from @PACKAGE_INIT@ by configure_package_config_file() #######
####### Any changes to this file will be overwritten by the next CMake run ####
####### The input file was beman.exemplar-config.cmake.in                            ########

get_filename_component(PACKAGE_PREFIX_DIR "${CMAKE_CURRENT_LIST_DIR}/../../../" ABSOLUTE)

macro(set_and_check _var _file)
  set(${_var} "${_file}")
  if(NOT EXISTS "${_file}")
    message(FATAL_ERROR "File or directory ${_file} referenced by variable ${_var} does not exist !")
  endif()
endmacro()

macro(check_required_components _NAME)
  foreach(comp ${${_NAME}_FIND_COMPONENTS})
    if(NOT ${_NAME}_${comp}_FOUND)
      if(${_NAME}_FIND_REQUIRED_${comp})
        set(${_NAME}_FOUND FALSE)
      endif()
    endif()
  endforeach()
endmacro()

####################################################################################

include(${CMAKE_CURRENT_LIST_DIR}/beman.exemplar-targets.cmake)

check_required_components(beman.exemplar)

What's the use case for adding this option?

I suppose this works for now, but ideally the version here would match the release version and the git tag. We need at least a release runbook for making sure that happens. Or we could provide GitHub actions that do the job, maybe leveraging things like the PYPI bumpversion package.

See: #112

What are your thoughts about just shipping one portable, executable test.cmake script and keeping things simple? As in: cmake -P test.cmake

Alternatively, we could ship this behavior as a CMake preset and just have: cmake --workflow user-test

Is there a way to get the formatter to accept something like this?
It's nice to have key/value pairs on separate lines for clarity if possible.

I'd prefer using paths relative to CMAKE_CURRENT_SOURCE_DIR and CMAKE_CURRENT_BINARY_DIR whenever possible. PROJECT_SOURCE_DIR and such are at a minimum confusing and often wrong when projects get combined into superbuild projects and such.

This goes for the whole PR, not just this file.

If we find all length or indirection annoying, fair, but we can make a local variable or even a special project-wide variable to clarify.

I guess I'll defer to advice in Professional CMake if you can provide references, but I expect Beman projects will be rather unstable, so I'd actually start Beman projects off with ExactVersion... or even skipping the version compatibility entirely (leaving it up to the package manager, git operations, etc.).

I'd rather not use PROJECT_NAME like this. It just obfuscates what's going on. The package name and the project name do match for this project, but they're different settings. I'd be fine just hardcoding beman.exemplar literally throughout this file, but if we want a self-documenting local variable like export_package_name, or something, that's fine too.

I don't like to call bat as sh scripts, because this is not portable.

And you see, this if else block should to the same, but it does't!

Too the CMAKE_CXX_STANDARD is a user defined value!

For CXX_MODULES, the build and test environment mast be absolute the same.