-
Who's Online 1 Member, 1 Anonymous, 962 Guests (See full list)
-
Topics
-
Posts
-
@Grautvornix Also note that I get the same error, even if I clear the build folder!
-
@Asher Thanks ! @Grautvornix this version is better but I have this : 39875 INFO: Graph cross-reference written to /home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator/xref-Mercator.html 39925 INFO: checking PYZ 39925 INFO: Building PYZ because PYZ-00.toc is non existent 39925 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz 41085 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz completed successfully. 41115 WARNING: Ignoring icon; supported only on Windows and macOS! 41126 INFO: checking PKG 41126 INFO: Building PKG because PKG-00.toc is non existent 41126 INFO: Building PKG (CArchive) Mercator.pkg 41144 INFO: Building PKG (CArchive) Mercator.pkg completed successfully. 41145 INFO: Bootloader /home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/bootloader/Linux-64bit-intel/run 41145 INFO: checking EXE 41145 INFO: Building EXE because EXE-00.toc is non existent 41145 INFO: Building EXE from EXE-00.toc ERROR: The output directory "/home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator" is not empty. Please remove all its contents or use the -y option (remove output directory without confirmation).
-
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
-
By Grautvornix · Posted
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
-
