Hi,
I've codeblocks windows version svn 3758.
When I try to excecute my compiled program in codeblocks I obtain this:
Checking for existence: E:\test\test\bin\Release\test.exe
Executing: D:\Programmi\codeblocks/cb_console_runner.exe "E:\test\test\bin\Release\test.exe" (in E:\test\test\.)
Execution of ' D:\Programmi\codeblocks/cb_console_runner.exe "E:\test\test\bin\Release\test.exe" ' in 'E:\test\test' failed.
Nothing to be done.
The executable test.exe is correctly placed in E:\test\test\bin\Release\;
I've tried to run it manually and it works fine.
I've tried to manually do this command from prompt:
cb_console_runner E:\test\test\bin\Release\test.exe
and it works fine.
I think the problem is in the call to cb_console_runner;
in fact in the error I see:
D:\Programmi\codeblocks/cb_console_runner.exe
I think the slash must be replaced by backslash.
Let me know...
pv
should have been fixed with r3759 ?
It may be;
but, HOw must I do to download svn 3759 for windows?
I've downloaded latest windows nightly builds;
and it results to me svn 3758.
Is there a new link?
On linux I've latest svn version, but I can't try now.
Thank you
pv
Just wait for the next nightly. :-)
Has this issue been fixed/tested under Windows? I have the following issue that I think it the same problem.
I'm using "svn build rev 3811 (2007-04-04 00:22:46) gcc 3.4.5 Windows/unicode"
Code::Blocks seems to mix backslashes and slashes in the same path. I'm compiling an app that uses physfs, and it
doesn't work out very well.
If I set:
Project Properties
Build Targets
Output filename: whatever.exe
Then the argv[0] will turn out to be something like
"C:\something\whatever/whatever.exe"
If I set it to:
Project Properties
Build Targets
Output filename: C:\something\whatever\whatever.exe
Then the argv[0] will turn out to be "C:\something\whatever\whatever.exe"
Is there something that I can do to resolve this, because I would like my
project files to be portable. I don't like having the absolute path in
there, but if I don't do it, things won't run from inside of the debugger
properly. Note that it always seems fine when run outside of the debugger.
Only change made was regarding space, slashes vs. backslashes are left to do (AFAIK)