-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into woptim/spack-envs
- Loading branch information
Showing
89 changed files
with
356 additions
and
275 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,58 +1,28 @@ | ||
# - caliper: Context Annotation Library | ||
# | ||
#============================================================================= | ||
# Caliper is a program instrumentation and performance measurement | ||
# framework. It provides data collection mechanisms and a source-code | ||
# annotation API for a variety of performance engineering use cases, | ||
# e.g., performance profiling, tracing, monitoring, and | ||
# auto-tuning. | ||
# | ||
#=== Usage =================================================================== | ||
# This file allows caliper to be automatically detected by other libraries | ||
# using CMake. To build with caliper, you can do one of two things: | ||
# | ||
# 1. Set the caliper_DIR environment variable to the root of the Caliper | ||
# installation. If you loaded caliper through a dotkit, this may already | ||
# be set, and caliper will be autodetected by CMake. | ||
# | ||
# 2. Configure your project with this option: | ||
# -Dcaliper_DIR=<caliper install prefix>/share/ | ||
# | ||
# If you have done either of these things, then CMake should automatically find | ||
# and include this file when you call find_package(caliper) from your | ||
# CMakeLists.txt file. | ||
# | ||
#=== Components ============================================================== | ||
# (David's TO DO) | ||
# | ||
# To link against these, just do, for example: | ||
# | ||
# find_package(caliper REQUIRED) | ||
# add_executable(foo foo.c) | ||
# target_link_libraries(foo caliper) | ||
# | ||
# That's all! | ||
# | ||
if (NOT caliper_CONFIG_LOADED) | ||
set(caliper_CONFIG_LOADED TRUE) | ||
@PACKAGE_INIT@ | ||
|
||
# Install layout | ||
set(caliper_INSTALL_PREFIX @CMAKE_INSTALL_PREFIX@) | ||
set(caliper_INCLUDE_DIR @CMAKE_INSTALL_FULL_INCLUDEDIR@) | ||
set(caliper_LIB_DIR @CMAKE_INSTALL_FULL_LIBDIR@) | ||
set(caliper_CMAKE_DIR @CMAKE_INSTALL_FULL_DATADIR@/cmake/caliper) | ||
include(CMakeFindDependencyMacro) | ||
|
||
# Includes needed to use caliper | ||
set(caliper_INCLUDE_PATH ${caliper_INCLUDE_DIR}) | ||
set(caliper_LIB_PATH ${caliper_LIB_DIR}) | ||
include("${CMAKE_CURRENT_LIST_DIR}/caliper-targets.cmake") | ||
|
||
include(CMakeFindDependencyMacro) | ||
find_dependency(Threads) | ||
set_and_check(caliper_INCLUDE_DIR "@PACKAGE_caliper_INSTALL_INCLUDE_DIR@") | ||
|
||
if (@CALIPER_HAVE_ADIAK@) | ||
find_dependency(adiak) | ||
if (@CALIPER_HAVE_ADIAK@) | ||
if (NOT TARGET adiak::adiak) | ||
set(CALIPER_ADIAK_DIR @adiak_DIR@) | ||
if (NOT adiak_DIR) | ||
set(adiak_DIR ${CALIPER_ADIAK_DIR}) | ||
endif() | ||
find_dependency( | ||
adiak | ||
CONFIG | ||
NO_DEFAULT_PATH | ||
PATHS | ||
${adiak_DIR} | ||
${adiak_DIR}/lib/cmake/adiak | ||
${PACKAGE_PREFIX_DIR} | ||
${PACKAGE_PREFIX_DIR}/lib/cmake/adiak | ||
) | ||
endif() | ||
|
||
# Library targets imported from file | ||
include(${caliper_CMAKE_DIR}/caliper-targets.cmake) | ||
endif() | ||
|
||
check_required_components(caliper) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.