在Mac上安装Google Football时出现错误

如何解决在Mac上安装Google Football时出现错误

我正在尝试在运行Catalina 10.15.7的Mac上安装Google Football。和Xcode 12.0，我已经按照网站上显示的说明使用Homebrew安装所需的软件包，但是当我尝试使用以下命令运行该软件时：

python3 -m gfootball.play_game --action_set=full

我收到以下消息：

WARNING:root:Looks like game engine is not compiled,please run:
WARNING:root:  pushd /usr/local/lib/python3.8/site-packages/gfootball_engine && cmake . && make -j `nproc` && popd
WARNING:root:  pushd /usr/local/lib/python3.8/site-packages/gfootball_engine && ln -s libgame.so _gameplayfootball.so && popd
Traceback (most recent call last):
  File "/usr/local/Cellar/python@3.8/3.8.5/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py",line 185,in _run_module_as_main
    mod_name,mod_spec,code = _get_module_details(mod_name,_Error)
  File "/usr/local/Cellar/python@3.8/3.8.5/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py",line 111,in _get_module_details
    __import__(pkg_name)
  File "/usr/local/lib/python3.8/site-packages/gfootball/__init__.py",line 17,in <module>
    from gfootball.env import scenario_builder
  File "/usr/local/lib/python3.8/site-packages/gfootball/env/__init__.py",line 21,in <module>
    from gfootball.env import config
  File "/usr/local/lib/python3.8/site-packages/gfootball/env/config.py",line 24,in <module>
    import gfootball_engine as libgame
  File "/usr/local/lib/python3.8/site-packages/gfootball_engine/__init__.py",line 39,in <module>
    from _gameplayfootball import *
ImportError: dlopen(/usr/local/lib/python3.8/site-packages/gfootball_engine/_gameplayfootball.so,2): no suitable image found.  Did find:
    /usr/local/lib/python3.8/site-packages/gfootball_engine/_gameplayfootball.so: unkNown file type,first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x03
    /usr/local/lib/python3.8/site-packages/gfootball_engine/_gameplayfootball.so: unkNown file type,first eight bytes: 0x7F 0x45 0x4C 0x46 0x02 0x01 0x01 0x03

按照我随后运行的消息中显示的指导进行操作：

/usr/local/lib/python3.8/site-packages/gfootball_engine /usr/local/lib/python3.8/site-packages/gfootball_engine ~/Desktop
Using Python: 3.8.6
-- Could NOT find Boost: missing: python3-py38 (found /usr/local/lib/cmake/Boost-1.73.0/BoostConfig.cmake (found version "1.73.0"))
python3-py38 not found. Trying other names.
-- Could NOT find Boost: missing: python-py38 (found /usr/local/lib/cmake/Boost-1.73.0/BoostConfig.cmake (found version "1.73.0"))
python-py38 not found. Trying other names.
-- Found Boost: /usr/local/lib/cmake/Boost-1.73.0/BoostConfig.cmake (found version "1.73.0") found components: python38 
Using python_boost: python38
-- Found Boost: /usr/local/lib/cmake/Boost-1.73.0/BoostConfig.cmake (found version "1.73.0") found components: thread system filesystem python38 
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/lib/python3.8/site-packages/gfootball_engine
zsh: command not found: nproc
[  0%] Built target managerslib
[  0%] Built target systemscommonlib
[  2%] Built target loaderslib
[  5%] Built target typeslib
[  8%] Built target datalib
[ 14%] Built target utilslib
[ 20%] Built target menulib
[ 28%] Built target gui2lib
[ 40%] Built target baselib
[ 50%] Built target systemsgraphicslib
[ 62%] Built target scenelib
[ 64%] Built target blunted2
[ 88%] Built target gamelib
[100%] Built target game
/usr/local/lib/python3.8/site-packages/gfootball_engine ~/Desktop

我检查了是否安装了nproc（使用pip3 list），但是我不确定为什么找不到它。当我使用第二条警告消息中显示的建议时：

pushd /usr/local/lib/python3.8/site-packages/gfootball_engine && ln -s libgame.so _gameplayfootball.so && popd

我收到以下消息：

/usr/local/lib/python3.8/site-packages/gfootball_engine /usr/local/lib/python3.8/site-packages/gfootball_engine /usr/local/lib/python3.8/site-packages/gfootball_engine ~/Desktop
ln: _gameplayfootball.so: File exists

“文件存在”消息提示编译的游戏引擎位于错误的文件夹中，但我不确定。我已经检查了文件夹的数量，并且一切似乎都到位，例如我正在Homebrew文件夹中使用python版本，例如python@3.8。

我是Python的新手，所以很可能让自己陷入了编译和文件夹的泥潭。感谢您对下一步可以解决该问题的任何帮助-谢谢。

解决方法

经过进一步的调查，我发现如我所料，我陷入了混乱。有两种安装模块的方法。第一种方法是使用pip3：

pip3 install gfootball

第二种方法是从GitHub存储库构建gfootball，然后使用：

pip3 install . 

是从内置文件夹中获取的。但是，两种方式仍然会出现相同的错误。