User forums > General (but related to Code::Blocks)
CodeBlocks being called from hudson (on linux)
Jenna:
--- Quote from: MortenMacFly on January 05, 2011, 04:56:59 pm ---
--- Quote from: jens on January 05, 2011, 07:35:28 am ---svn-repo on my server : svn://jenslody.de/codeblocks-console/trunk
--- End quote ---
Jens, don't you think we should create a branch for this on the main repo?
--- End quote ---
Of course we can do so.
There have been two reasons to create it on my server:
the first is, that it was not (yet) meant to be published, more as a proof of concept,
the second is, that I wanted to create my own repo to learn how to do it, because it's much easier to maintain my patches, if I have a repo somewhere outside my developping systems, because I can reach it easily from everywhere and from all my (partly virtual) systems.
MortenMacFly:
--- Quote from: jens on January 05, 2011, 05:14:07 pm ---There have been two reasons to create it on my server: [...]
--- End quote ---
I see. So just keep it in mind for the future... For community development and browsing/tracking of the changes BerliOS would be better IMHO.
san:
It seems that there still is a dependency on wxWidgets for codeblocks-console. I don't have wxWidgets installed on my FreeBSD machine and if it's possible like to keep it this way.
Bootstrap returns with the following error (I get a lot of warnings).
--- Code: ---#./bootstrap
[...]
configure.in:77: error: possibly undefined macro: AM_OPTIONS_WXCONFIG
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:78: error: possibly undefined macro: AM_PATH_WXCONFIG
--- End code ---
Jenna:
--- Quote from: san on January 06, 2011, 10:26:40 am ---It seems that there still is a dependency on wxWidgets for codeblocks-console. I don't have wxWidgets installed on my FreeBSD machine and if it's possible like to keep it this way.
Bootstrap returns with the following error (I get a lot of warnings).
--- Code: ---#./bootstrap
[...]
configure.in:77: error: possibly undefined macro: AM_OPTIONS_WXCONFIG
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:78: error: possibly undefined macro: AM_PATH_WXCONFIG
--- End code ---
--- End quote ---
Not without rewriting great parts of C::B from scratch.
Jenna:
--- Quote from: MortenMacFly on January 05, 2011, 05:36:14 pm ---
--- Quote from: jens on January 05, 2011, 05:14:07 pm ---There have been two reasons to create it on my server: [...]
--- End quote ---
I see. So just keep it in mind for the future... For community development and browsing/tracking of the changes BerliOS would be better IMHO.
--- End quote ---
Okay, it was nice to play with, but it is really hard to keep in sync with trunk, so a possible merge (if it ever happens) will be quite difficult.
Is it enough if I do a "svn copy ..." to create a new branch, or do I need special rights on the berlios server ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version