lumberyard-employee-dm
0ad2fe2294
* Implemented the RFC to allow projects to need to specify the Gems Projects no longer need to specify CMake Targets to associate a Gem variant with. In order to associate a CMake Target with a gem variant a new `ly_set_gem_variant_to_load` function has been added that maps CMake Targets -> Gem Variants. This allows CMake Targets to self describe which gem variants they desire to build and load This implementation is backwards compatible: The `ly_enable_gems` function still accepts the TARGETS and VARIANTS arguments which it will forward to the new `ly_set_gem_variant_to_load` function to allow the input Targets to be associated with input Gem Variants This changes fixes the issue with gems that are required by an Application regardless of the Project in use, not replicating it's "requiredness" to the SDK layout Fixes #3430 Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Added an LY_PROJECT_NAME property to the Launcher targets The `ly_enable_gems_delayed` now command queries the LY_PROJECT_NAME property associated with each target to determine if the gems being enabled are match the project the target is associated with. In this case the target only adds dependencies if the gems is being enabled without a specific project or if the gems is being enabled for the matching project. If the LY_PROJECT_NAME property is not set for target, it indicates the gems for each project can be added as dependencies to the target. Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * The INSTALL step now forwards the LY_PROJECT_NAME property for a target The Install_common.cmake has been updated to support configuring TARGET_PROPERTIES into the generated CMakeLists.txt for install targets. Furthermore the indentation of the generated CMakeLists.txt has been normalized to help with readability Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Updating the Atom_Bootstrap CMakeLists.txt to enable the Atom_Bootstrap Gem Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Added a deprecation message to ly_enable_gems when supplying TARGETS and VARIANTS Added a define_property call for the LY_PROJECT_NAME target property Removed the .Builders alias for the PrefabBuilder and renamed the GEM_MODULE target o PrefabBuilder.Builders. Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Removed superflous space from AutomatedTesting Gem CMakeLists.txt Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com>
80 lines
3.4 KiB
CMake
80 lines
3.4 KiB
CMake
# {BEGIN_LICENSE}
|
|
# Copyright (c) Contributors to the Open 3D Engine Project.
|
|
# For complete copyright and license terms please see the LICENSE at the root of this distribution.
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0 OR MIT
|
|
#
|
|
# {END_LICENSE}
|
|
|
|
# Currently we are in the ${Name}/Code folder: ${CMAKE_CURRENT_LIST_DIR}
|
|
# Get the platform specific folder ${pal_dir} for the current folder: ${CMAKE_CURRENT_LIST_DIR}/Platform/${PAL_PLATFORM_NAME}
|
|
# Note: ly_get_list_relative_pal_filename will take care of the details for us, as this may be a restricted platform
|
|
# in which case it will see if that platform is present here or in the restricted folder.
|
|
# i.e. It could here : ${Name}/Code/Platform/<platorm_name> or
|
|
# <restricted_folder>/<platform_name>/${Name}/Code
|
|
ly_get_list_relative_pal_filename(pal_dir ${CMAKE_CURRENT_LIST_DIR}/Platform/${PAL_PLATFORM_NAME} ${o3de_project_restricted_path} ${o3de_project_path} ${o3de_project_name})
|
|
|
|
# Now that we have the platform abstraction layer (PAL) folder for this folder, thats where we will find the
|
|
# traits for this platform. Traits for a platform are defines for things like whether or not something in this project
|
|
# is supported by this platform.
|
|
include(${pal_dir}/PAL_${PAL_PLATFORM_NAME_LOWERCASE}.cmake)
|
|
|
|
# Now that we have loaded our project traits for this platform, see if this project is even supported on this platform.
|
|
# If its not supported we just return after including the unsupported.
|
|
if(NOT PAL_TRAIT_${NameUpper}_SUPPORTED)
|
|
return()
|
|
endif()
|
|
|
|
# We are on a supported platform, so add the ${Name} target
|
|
# Note: We include the common files and the platform specific files which are set in ${NameLower}_files.cmake and
|
|
# in ${pal_dir}/${NameLower}_${PAL_PLATFORM_NAME_LOWERCASE}_files.cmake
|
|
ly_add_target(
|
|
NAME ${Name}.Static STATIC
|
|
NAMESPACE Gem
|
|
FILES_CMAKE
|
|
${NameLower}_files.cmake
|
|
${pal_dir}/${NameLower}_${PAL_PLATFORM_NAME_LOWERCASE}_files.cmake
|
|
INCLUDE_DIRECTORIES
|
|
PUBLIC
|
|
Include
|
|
BUILD_DEPENDENCIES
|
|
PRIVATE
|
|
AZ::AzGameFramework
|
|
Gem::Atom_AtomBridge.Static
|
|
)
|
|
|
|
ly_add_target(
|
|
NAME ${Name} ${PAL_TRAIT_MONOLITHIC_DRIVEN_MODULE_TYPE}
|
|
NAMESPACE Gem
|
|
FILES_CMAKE
|
|
${NameLower}_shared_files.cmake
|
|
${pal_dir}/${NameLower}_shared_${PAL_PLATFORM_NAME_LOWERCASE}_files.cmake
|
|
INCLUDE_DIRECTORIES
|
|
PUBLIC
|
|
Include
|
|
BUILD_DEPENDENCIES
|
|
PRIVATE
|
|
Gem::${Name}.Static
|
|
AZ::AzCore
|
|
)
|
|
|
|
# if enabled, ${Name} is used by all kinds of applications
|
|
ly_create_alias(NAME ${Name}.Builders NAMESPACE Gem TARGETS Gem::${Name})
|
|
ly_create_alias(NAME ${Name}.Tools NAMESPACE Gem TARGETS Gem::${Name})
|
|
ly_create_alias(NAME ${Name}.Clients NAMESPACE Gem TARGETS Gem::${Name})
|
|
ly_create_alias(NAME ${Name}.Servers NAMESPACE Gem TARGETS Gem::${Name})
|
|
|
|
################################################################################
|
|
# Gem dependencies
|
|
################################################################################
|
|
|
|
# Enable the specified list of gems from GEM_FILE or GEMS list for this specific project:
|
|
ly_enable_gems(PROJECT_NAME ${Name} GEM_FILE enabled_gems.cmake)
|
|
|
|
if(PAL_TRAIT_BUILD_SERVER_SUPPORTED)
|
|
# this property causes it to actually make a ServerLauncher.
|
|
# if you don't want a Server application, you can remove this and the
|
|
# following ly_enable_gems lines.
|
|
set_property(GLOBAL APPEND PROPERTY LY_LAUNCHER_SERVER_PROJECTS ${Name})
|
|
endif()
|