o3de / o3de

Open 3D Engine (O3DE) is an Apache 2.0-licensed multi-platform 3D engine that enables developers and content creators to build AAA games, cinema-quality 3D worlds, and high-fidelity simulations without any fees or commercial obligations.
https://o3de.org
Other
7.81k stars 2.2k forks source link

Project configuration fails if newly created gems are added to the Project #6956

Closed LB-TomaszSerwanski closed 2 years ago

LB-TomaszSerwanski commented 2 years ago

Describe the bug If newly created Gems are added to the Project, it fails to configure due to the following error:

CMake Error at D:/Gems/PythonTool/CMakeLists.txt:5 (o3de_restricted_path):
  o3de_restricted_path Function invoked with incorrect arguments for function
  named: o3de_restricted_path
CMake Deprecation Warning at D:/Git/o3de/cmake/PAL.cmake:388 (message):
  ly_get_list_relative_pal_filename is being deprecated, change your code to
  use o3de_pal_dir instead.
Call Stack (most recent call first):
  D:/Gems/Nowe/PythonTool/Code/CMakeLists.txt:8 (ly_get_list_relative_pal_filename)

Please note that due to #6955 this has only been verified on AutomatedTesting.

Please also note that the issue is probably caused by commit c778606.

Refer to the attached log file for more details.

Steps to reproduce Steps to reproduce the behavior:

  1. Create a new Gem from any of the templates, i.e. _"\scripts\o3de.bat create-gem --gem-path C:/PythonTool --template-name PythonToolGem"_
  2. Register the Gem in the Project: _"\scripts\o3de register -gp C:/PythonTool -espp AutomatedTesting"_
  3. Enable the Gem in the Project: _"\scripts\o3de enable-gem -gp C:/PythonTool -pp AutomatedTesting"_
  4. Configure the Project: _"cmake -B build/windows_vs2019 -S . -G "Visual Studio 16" -DLY_3RDPARTYPATH=C:\o3de-packages"

Expected behavior Project configuration is successful.

Actual behavior Project configuration fails.

Screenshots/Video

ProjectConfigurationFails

Found in Branch Development (76ff7ae)

Desktop/Device:

Attachments configure_log.txt

LB-KacperBieniek commented 2 years ago

Verified the issue is fixed in latest development (3bbb8d7) thanks to this pull request: https://github.com/o3de/o3de/pull/6976.