User forums > Using Code::Blocks

Non-interactive building with Code::Blocks

(1/2) > >>

paavo512:
Hi,

Is there any way to force C::B to run in a non-interactive way, like a --non-interactive command line option (which is not there) or something like that, so there would be no dialog boxes, ever? I'm asking as we are using it in nightly builds on Linux, on headless servers and there is nobody watching the screen or clicking the OK buttons. It appears it sometimes wants to display some random dialogs, like "Another program instance is currently running" or some crash report window or something (it is also crashing really often, but this is another topic). It would be much preferable if it just dumped the error message to stderr and exited with an error code.

TIA
Paavo

stahta01:
There is or was a console build somewhere in SVN for Linux users with your problem.

Try looking for branch codeblocks_console.

Tim S.

paavo512:

Thanks for the response, I will try it out. First tests show that at least the "Another program instance is currently running" dialog box is still present. Maybe I can hack the code myself to deal with this.

Cheers
Paavo

oBFusCATed:

--- Quote from: paavo512 on April 17, 2013, 12:43:24 pm ---Thanks for the response, I will try it out. First tests show that at least the "Another program instance is currently running" dialog box is still present. Maybe I can hack the code myself to deal with this.

--- End quote ---
There are command line options, which should help you to fix this (--multiple-instances probably).

Jenna:

--- Quote from: paavo512 on April 17, 2013, 12:43:24 pm ---
Thanks for the response, I will try it out. First tests show that at least the "Another program instance is currently running" dialog box is still present. Maybe I can hack the code myself to deal with this.

--- End quote ---

Definitely in the in the console-version.

It is really headless and works on servers without xserver.

It's in: http://sourceforge.net/p/codeblocks/code/HEAD/tree/branches/codeblocks_console/ and linux-only (might also work on mac).
I did not update it for a long time and it is not a clean, but more or less hackky solution. Nevertheless it works fine with the conf-file up to release 12.11, but probaly not with the conf-files from trunk.

Navigation

[0] Message Index

[#] Next page