I tried building CodeBlocks in Linux (Fedora Core 6) with wxWidgets 2.8.3 Monolithic\Shared\Unicode\Release build.
I used four patches mentioned in:
http://forums.next.codeblocks.org/index.php/topic,5783.0.html (3 patches here)
http://developer.berlios.de/bugs/?func=detailbug&bug_id=10881&group_id=5358 (1 patch here)
"svn build rev 3976 (2007-05-20 18:49:23) gcc 4.1.1 Linux/Unicode"
CodeBlocks was built and when started it hangs. Sometimes the IDE gets properly rendered, other times it doesn't.
It doesn't give out any warnings and there are no errors and warnings in the terminal when even when the program is ran from a terminal.
I tried running it after removing some of the plugins and i figured out that the problem is due to the "compiler plugin" (libcompiler.so)
Switch to wxGTK 2.8.4. wxGTK 2.8.3 has this hang at start-up bug.
thanks i'll try that
I've run into the same problems. I was hoping to just use ubuntu's wxgtk2.8-dev... how far behind are the main ubuntu repositories?
is there any reason that C::B has to have a near bleeding edge dependency on wx?
Quote from: dmoore on May 21, 2007, 01:28:45 PM
is there any reason that C::B has to have a near bleeding edge dependency on wx?
None at all. Feel free to build C::B using the wx2.6 packages in ubuntu (that's what I do).
Yes under 2.6 even I had no problems, but then I decided to switch to the 2.8.3 version and had this problem of windows hang on startup.
Now I build it with wx-GTK.2.8.4 and it is working fine but some of the controls are not rendered properly like the drop down on compiler settings is too small.
Anyway hang at startup is now gone using wx-GTK-2.8.4.
Looks like there is a 2.8.4 package available for Ubuntu and Debian. I'm in the process of trying out a build. I'll let you know how it goes.
http://www.wxwidgets.org/downloads/ (http://www.wxwidgets.org/downloads/)
EDIT: Success! See my post here. http://forums.next.codeblocks.org/index.php/topic,5956.msg45602/topicseen.html#msg45602 (http://forums.next.codeblocks.org/index.php/topic,5956.msg45602/topicseen.html#msg45602)
thanks guys.
some follow up (debian) newbie questions:
1. it appears that there are at least two ways to switch between wxWidgets versions for compilation,
sudo update-alternatives --config wx-config
alternatively go into the cb project files and change all instances of wx-config to $wx-config and define variable wx-config as /path/to/desired/version/wx-config. is that correct?
2. is update-alternatives supported in all debian packages by default? For example, if I want to maintain several nightlies of codeblocks on my system, can I use update-alternatives to switch between them or would Mandrav need to do some magic (assuming he hasn't already) for that to happen?