User forums > General (but related to Code::Blocks)

CodeBlocks being called from hudson (on linux)

<< < (5/10) > >>

killerbot:
I am afraid that hudson won't be able to understand the log file, or display it; since it is expecting raw text, but something to try ...
EDIT : did a cat of the build html file, it is better than nothing, but not the ultimate solution, one can not 'monitor' the build, since output only pops up at the end, and just a cat of a html file is not really readable.

EDIT 2 : in this setup, when a build error occurs, hudson has no clue of it, probably for 2 reasons :
- it can't scan anything on stdout (if it already does this)
- the return value of CB/compiler is probably not propagated due to the xinit ?

san:
Jens, it would be great if there would be an option to build codeblocks projects without the need for an X server. It would make it possible to run automated nightly builds on a dedicated server.

Don't mean to hijack this thread but when attempting to do nightly builds without the need for an X server leads to a search for other buildsystems and purely use codeblocks as an advanced text editor. Right now I'm looking at Waf and Scons which seems both flexible. And are there plans to support other other build systems (like Makefiles) from codeblocks?

Jenna:
C::B partly supports makefiles.
It can call them, but in this case it is really just a better editor (with code-completion etc.), but the power of C::B's build-system can not be used.

killerbot:
one very powerfull use case of CB as a build system, is when you have code to be compiled for different platforms, or just with different compilers.

Example : a library
- target 1 : gcc debug
- target 2 : gcc release
- target 3 : cross compiler debug
- target 4 : cross compiler release
- and so on

Just tell CB to build the cbp project file, and you get all of them, much easier compared to make files. Note it will no always be the best tool for the job, but in many use cases it is.

Basically : can the build engine of CB get a non gui front-end, and in such a way that it can start up without an x server being present.

EDIT : the batch builds are a first step, but seems we need a bit more.

Jenna:
@killerbot:
do you use 64-bit or 32-bit linux ?
Which distro do you use ?

I just revived the ugly, hacky "ifdef"-console-C::B. I had to apply the 190kB patch manually, but now it works.
I just compile dthe whole C::B (core and contrib-plugins) on a real console (not virtual terminal).

I test it on other distros (centos will be the first) and see if it works there without recompiling.

That's a first step (and proof of concept). Now I will try to split the relevant sources in base and gui-parts.

Navigation

[0] Message Index

[#] Next page

[*] Previous page