On macOS, after installing axmol 2.11.4 from the zip file downloaded from the Releases page, I executed the command axmol new from pwsh, but instead creating a new project, the file called axmol from axmol/tools/cmdline opened in plain text.
With the help of rh101 we found the issue is the privileges of that file: when downloading from the zip, they are -rw-rw-r--. Changing them using the command chmod +x axmol solves the problem.
Testing the cloned version from GitHub, there is no issue: the privileges of that file are -rwxrwxr-x, so it works.
It is possible for setup.ps1 to automatically fix the permissions on any bash used in the engine, for the people using the zip files on macOS? If it's not possible, we'll add the chmod +x solution to the FAQ.
On macOS, after installing axmol 2.11.4 from the zip file downloaded from the Releases page, I executed the command
axmol newfrompwsh, but instead creating a new project, the file calledaxmolfromaxmol/tools/cmdlineopened in plain text.With the help of rh101 we found the issue is the privileges of that file: when downloading from the zip, they are
-rw-rw-r--. Changing them using the commandchmod +x axmolsolves the problem.Testing the cloned version from GitHub, there is no issue: the privileges of that file are
-rwxrwxr-x, so it works.It is possible for
setup.ps1to automatically fix the permissions on any bash used in the engine, for the people using the zip files on macOS? If it's not possible, we'll add thechmod +xsolution to the FAQ.