Nov 4, 2013 at 11:55 AM
after I Build the SDK I'm trying to run the test in Binaries/Debug64. But I'm getting this message:
bash: ./ /bin/bash^M: bad interpreter: No such file or directory   
What does it mean?

Nov 5, 2013 at 11:44 PM
This issue happens when the script file is edited in windows environment and then ported and executed on Linux.
Text files created on DOS/Windows machines have different line endings than files created on Unix/Linux. Hence it is seeing ^M as an illegal character.

You can try dos2unix to convert the file.

Please refer to this stackoverflow article for more details.

Nov 6, 2013 at 2:54 AM
My bad, I had verified that the file does not contain ^M when I pull from the GIT repositories (master as well as development). And jumped to the conclusion that our sources are fine. Looks like GIT takes care of removing the characters.

Now, I downloaded the source directly from codeplex and it contains the ^M characters.

We will definitely fix this. But until the fix propagates to the master branch, you could use the workaround I suggested above.

Nov 6, 2013 at 7:23 AM
I've tried the dos2unix solution und now it's working. Thanks for the fast response.