Build run with errors, but errors what?

[groggily]

This is the most useless error message I have ever seen. Based on what I have experienced, I think it can't see the compiler binary. But why? I even used absolute path to the compiler binary. It still tell me the same error message. I go to the built-in terminal emulator and I could compile the program without any issues.

p/s: Linux

[SpartanJ]

I think it can't see the compiler binary.

I just added a warning for this case, there was a warning for an invalid working dir but not for not finding the binary.

But why?

If you're not using an absolute path, there are two possible reasons I can think of:

• Binary is not in PATH.
• You're using arguments in the command parameter.

I even used absolute path to the compiler binary. It still tell me the same error message.

There are few possible reasons if you're using an absolute path, all I can think of is:

• Incorrect absolute path
• You're using arguments in the command parameter.

[groggily]

Binary is in PATH but ecode can't see it! I'm not putting arguments in the command field. Absolute path is correct.

[groggily]

Fixed with the latest commit.