Source release 17.1.1
This commit is contained in:
53
platforms/example-runtime-client-info/environment.py
Normal file
53
platforms/example-runtime-client-info/environment.py
Normal file
@@ -0,0 +1,53 @@
|
||||
# Copyright 2022 Google LLC. All Rights Reserved. This file and proprietary
|
||||
# source code may only be used and distributed under the Widevine License
|
||||
# Agreement.
|
||||
|
||||
# GYP supports the following environment variables to control the paths to the
|
||||
# toolchain:
|
||||
#
|
||||
# * CC - The C compiler
|
||||
# * CXX - The C++ compiler
|
||||
# * AR - The archive tool
|
||||
# * NM - The symbol name tool
|
||||
# * READELF - The ELF metadata tool
|
||||
#
|
||||
# If any are not specified, they default to the system's installed copy of that
|
||||
# tool.
|
||||
#
|
||||
# Note that overriding the linker is NOT supported. The C or C++ compiler will
|
||||
# always be used as a front-end to the linker.
|
||||
#
|
||||
# Any of these may have "_host" or "_target" appended to indicate that they
|
||||
# should only be used when compiling for the host or for the target when
|
||||
# cross-compiling. If GYP is cross-compiling and a specific "_host" or "_target"
|
||||
# tool is not found, it will fall back to the normal tool. e.g. If there is no
|
||||
# "CC_host", host builds will use "CC".
|
||||
#
|
||||
# It is recommended to always set GYP_CROSSCOMPILE to 1 when cross-compiling.
|
||||
|
||||
# |export_variables| is a dictionary containing the variables to set. Relative
|
||||
# paths are interpreted as being relative to this file.
|
||||
export_variables = {
|
||||
# Although we aren't actually cross-compiling in this build, settings.gypi
|
||||
# relies on the cross-compiler's separation of host and target build
|
||||
# artifacts. By setting this variable, we force GYP to use cross-compilation
|
||||
# mode even though both modes use the same compiler binary.
|
||||
'GYP_CROSSCOMPILE': '1',
|
||||
|
||||
# Typically, you will want to set these to the paths to your system's
|
||||
# toolchain. but for this example, we'll just use the system install of GCC.
|
||||
'CC': 'gcc',
|
||||
'CXX': 'g++',
|
||||
'AR': 'ar',
|
||||
|
||||
# Alternatively, here's how you could use the GCC as the "host" toolchain and
|
||||
# Clang as the "target" toolchain:
|
||||
|
||||
# 'CC_target': 'clang',
|
||||
# 'CXX_target': 'clang++',
|
||||
# 'AR_target': 'llvm-ar',
|
||||
#
|
||||
# 'CC_host': 'gcc',
|
||||
# 'CXX_host': 'g++',
|
||||
# 'AR_host': 'ar',
|
||||
}
|
||||
Reference in New Issue
Block a user