Issues with "run" command in scripting project

[cellulose]

Hey all.

I'm currently working on Windows with a modified version of Code::Blocks that can be found on these forums.  It's similar to C::B 10.04, being based on a nightly from some months after, and enables "intellisense" for Angelscript.  It's working fine as far as I can tell.

To get it to boot up my script-integrated application, I set the "executable location" to the relative path in my SVN from the project file to the binary.  I set the project to use a "custom makefile" and deleted all the custom makefile commands.  And it works quite well, on my machine.  Build commands are always "nothing to be done" for now, and run boots the program promptly.  Unfortunately my collaborators don't seem to have the same experience.  On their machine, the run command produces no result -- not on Code::Blocks' logs, not in console output when running it from CMD.EXE.

Is there any kind of check that would take exception to my little hack?  Further, is there a way I can simply set a console command for the run button rather than booting an executable with command-line arguments?

[MortenMacFly]

with a modified version of Code::Blocks that can be found on these forums.

We cannot and don't provide support for forks. Sorry. Please ask the maintainer of that release to help.

Topic locked.