Jump to content

Forums

  1. Welcome

    1. Announcements / News

      The latest. What is happening with 0 A.D. Stay tuned...

      5.4k
      posts
    2. Introductions & Off-Topic Discussion

      Want to discuss something that isn't related to 0 A.D. or Wildfire Games? This is the place. Come on in and introduce yourself. Get to know others who are using 0 A.D.

      38.7k
      posts
    3. Help & Feedback

      Here is where you can get help with your questions. Also be sure to tell us how we are doing. What can we improve? What do you wish we could do better? Your opinion matters to us!

      16.9k
      posts
  2. 0 A.D.

    1. General Discussion

      This is the place to post general stuff concerning the game. Want to express your love for hoplites or find people to play the game with? Want to share your stories about matches you have played or discuss historical connections to the game? These and any other topics which are related to the game, but don't have their own forums belong in this forum.

      51.3k
      posts
    2. Gameplay Discussion

      Discuss the game play of 0 A.D. Want to know why the game plays the way it does or offer suggestions for how to improve the game play experience? Then this is the forum.

      28.2k
      posts
    3. Game Development & Technical Discussion

      A forum for technical discussion about the development of 0 A.D. Feel free to ask questions of the developers and among yourselves.

      48.4k
      posts
    4. Art Development

      Open development for the game's art. Submissions, comments, and suggestions now open.

      30.4k
      posts
    5. Game Modification

      Do you have any questions about modifying the game? What will you need to do what you want to? What are the best techniques? Discuss Modifications, Map Making, AI scripting and Random Map Scripting here.

      46k
      posts
    6. Project Governance

      Forums for decision-making on issues where a consensus can't be reached or isn't sufficient. The committees are chosen from among the official team members, but to ensure an open and transparent decision process it's publically viewable.

      148
      posts
    7. 597
      posts
  • Topics

  • Posts

    • This is the problem @lilypoppy. I was getting this on linux too, I think I used --break-system-packages or something. This is how ai summarized it:     
    • The reason is pyinstaller makes the executable for whatever os you are using. I think I saw somewhere in the terminal output that it was converting exe to something so mac could use it
    • Here is the new build script and also new spec files (bug identified: On Linux the program is a file called Mercator, with no .exe, and PyInstaller writes it into its work folder, where the spec had already made a folder of that name. Both specs now work in build/<name>/, which is PyInstaller’s own layout. I do not know why this did not stop @Asher’s macOS build, since macOS has no .exe either. Will update all spec-files, both build scripts and deliver a new release 0.26.0 very soon (will be available from the initial post on this thread). For @lilypoppy and all Ubuntu or Debian users, the whole preparation of the build should be this one line:  sudo apt install python3-venv binutils libpython3.12 Attached are the new build.sh and the two new pyinstaller spec files. Things to know: The tool also needs the usual desktop libraries added (glib, OpenGL, xkbcommon and so on). A normal Linux desktop has them; a bare server would not. The Linux builds are large: about 269 MB each, against roughly 98 MB on Windows. The icon (icon.ico) is ignored on Linux; PyInstaller only supports it on Windows and macOS. The new release will 0.26 contain this: [fix] The new build scripts (build.sh and build.bat as well as mercator.spec and post-atlas.spec) and a slightly revised icon [new] It integrates the findings tab from post-atlas into mercator so to allow fixing any findings already in the tool itself without having to switch between tools anymore when creating a new map. This option is still there, however. The additional workflow and overall GUI is not yet as simple and as clear as I would like it to be. Will continue working on it. Post-Atlas.spec build.sh Mercator.spec
    • @lilypoppy Oops! Sorry for the trouble! there are actually two faults, both in build.sh, not in the specs: The cause. Debian and Ubuntu refuse pip install into the system Python (PEP 668). So nothing was installed, pyinstaller did not exist, and no build ran. The misleading end. The script carried on after every failure and printed “Success!”. Working on a better script! Will come out shortly.
    • @Grautvornix @Asher  Hi, the test doesn't seem to have worked: the build failed with externally-managed-environment (PEP 668) and pyinstaller: command not found, even though the script still printed "Success!".   :~/Téléchargements/atlas-tools-0.25.0$ bash build.sh atlas-tools build script build script version 1.2.0 =============================================== Collecting libs... error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install     python3-xyz, where xyz is the package you are trying to     install.          If you wish to install a non-Debian-packaged Python package,     create a virtual environment using python3 -m venv path/to/venv.     Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make     sure you have python3-full installed.          If you wish to install a non-Debian packaged Python application,     it may be easiest to use pipx install xyz, which will manage a     virtual environment for you. Make sure you have pipx installed.          See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. =============================================== Building Mercator... build.sh: ligne 13: pyinstaller : commande introuvable Done =============================================== Building Post-Atlas... build.sh: ligne 17: pyinstaller : commande introuvable Done =============================================== Success! The executables can be found under the dist folder    
×
×
  • Create New...