I went into Environment settings and tried changing "Shell to run commands with:" to /bin/bash. Here is the result after I clicked build.
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/bash: g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o: No such file or directory
Process terminated with status 127 (0 minute(s), 0 second(s))
1 error(s), 0 warning(s) (0 minute(s), 0 second(s))
Same thing happens with the default /bin/sh.
-------------- Build: Debug in testProject (compiler: GNU GCC Compiler)---------------
g++ -Wall -fexceptions -g -c /home/USER_NAME/Programing/testProject/main.cpp -o obj/Debug/main.o
/bin/sh: 0: Can't open g++ -Wall -fexceptions -g -c /home/USER_NAME/Programming/testProject/main.cpp -o obj/Debug/main.o
Process terminated with status 127 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
I tried clicking both Debug and Release, with both shell programs. Still shows this error message.
You see this message because path "obj/Debug/main.o" is invalid on Linux. You need to change your configuration to something like "./obj/Debug/main.o" or "/full/path/to/obj/Debug/main.o".
Sorry to say. but this is absolutely bullshit !!
What you mean is, that you have to prepend
./ to run executables from inside the folder they reside in.
This is not needed for the output or the input. Try e.g. redirecting with < or >.
This is also not needed if the exe is in a subfolder, in this case [relative_path_to_folder/[exe] is enough.
By the way. the single dot is just the relative path to the actual subfolder, so no difference to my last exampl.