You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
70 lines
3.1 KiB
70 lines
3.1 KiB
# @HEADER
|
|
# ************************************************************************
|
|
#
|
|
# TriBITS: Tribal Build, Integrate, and Test System
|
|
# Copyright 2013 Sandia Corporation
|
|
#
|
|
# Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation,
|
|
# the U.S. Government retains certain rights in this software.
|
|
#
|
|
# Redistribution and use in source and binary forms, with or without
|
|
# modification, are permitted provided that the following conditions are
|
|
# met:
|
|
#
|
|
# 1. Redistributions of source code must retain the above copyright
|
|
# notice, this list of conditions and the following disclaimer.
|
|
#
|
|
# 2. Redistributions in binary form must reproduce the above copyright
|
|
# notice, this list of conditions and the following disclaimer in the
|
|
# documentation and/or other materials provided with the distribution.
|
|
#
|
|
# 3. Neither the name of the Corporation nor the names of the
|
|
# contributors may be used to endorse or promote products derived from
|
|
# this software without specific prior written permission.
|
|
#
|
|
# THIS SOFTWARE IS PROVIDED BY SANDIA CORPORATION "AS IS" AND ANY
|
|
# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SANDIA CORPORATION OR THE
|
|
# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
|
|
# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
|
|
# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
|
|
# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
|
|
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
|
|
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
#
|
|
# ************************************************************************
|
|
# @HEADER
|
|
|
|
|
|
# @MACRO: dual_scope_set()
|
|
#
|
|
# Macro that sets a variable name both in the current scope and the
|
|
# parent scope.
|
|
#
|
|
# Usage::
|
|
#
|
|
# dual_scope_set(<varName> [other args])
|
|
#
|
|
# It turns out that when one calls ``add_subdirectory(<someDir>)`` or enters a
|
|
# ``FUNCTION`` that CMake actually creates a copy of all of the regular
|
|
# non-cache variables in the current scope in order to create a new set of
|
|
# variables for the ``CMakeLists.txt`` file in ``<someDir>``. This means that
|
|
# if you call ``set(SOMEVAR Blah PARENT_SCOPE)`` that it will not affect the
|
|
# value of ``SOMEVAR`` in the current scope! This macro therefore is designed
|
|
# to set the value of the variable in the current scope and the parent scope
|
|
# in one shot to avoid confusion.
|
|
#
|
|
# Global variables are different. When one moves to a subordinate
|
|
# ``CMakeLists.txt`` file or enters a ``FUNCTION``, then a local copy of the
|
|
# variable is *not* created. If one sets the variable locally, it will shadow
|
|
# the global variable. However, if one sets the global cache value with
|
|
# ``set(SOMEVAR someValue CACHE INTERNAL "")``, then the value will get
|
|
# changed in the current subordinate scope and in all parent scopes all in one
|
|
# shot!
|
|
#
|
|
macro(dual_scope_set VARNAME)
|
|
set(${VARNAME} ${ARGN} PARENT_SCOPE)
|
|
set(${VARNAME} ${ARGN})
|
|
endmacro()
|
|
|