#169 Make the Unix build script executable

ping?

None of us use unix to know if this works, but more importantly removing the python command would appear to break Windows use.

If you mean build.sh, isn't it Unix-only file?

Since I'm using macOS (a unix os) and Windows, my answer is YES.

But Windows can run build.sh in msys, cygwin (Just like in this script. You can find more here!)

If you remove python command, you need to add a shebang in the corresponding python file, which will lead to a unknown python version.

What's more, the current build script is already executable. (I pulled a pr about the build script before to make it work and it worked well on my both computers.) If you still don't understand, please leave a message below to let me know if I can help.

If you remove python command, you need to add a shebang in the corresponding python file

It's already there.

What's more, the current build script is already executable.

I just update the master branch and it is not executable:

$ stat -c "%a" build.sh                                                                                                       
644

it is not executable

You need to run bash build.sh. If you want to run it in the ./build.sh way, you need to be the root user. And that's why we set the Access Control Lists to 755 for txt2gam* scripts (we can't find a proper interpreter)

What root user you are talking about? Why ACLs has anything to do with this? I just want to set the executable bit for scripts that already have proper shebangs.

txt2gam utility is not a script but compiled executable, it can be "interpreted" by a virtual machine only.

by a virtual machine only

It seems like you have no ideas about *nix on Windows... So It's hard for me to explain it to you.

Yes, I have no idea how does that work on Windows. Update the PR to include only mode changes.

@Kevin_Smarts, this PR now only changes file modes and should not break anything on any platform.

Can confirm this makes sense and works on linux.