I am using CB for 5 months, and I build code from svn about every 2 weeks.
After svn update to revision 2396, the build proccess ended successfully but when execute CB, execution fails with the message (before creation of main window):
"Something has gone wrong inside Code:Blocks and it will terminate.... blah blah"
No messages in console, only "Aborted"....
I'm using wxGTK 2.6.3 under Gentoo Linux.
After removing of libprojectwizard.{la,so} CB starts normaly...
Hello,
On Ubuntu 5.10 it works fine.
May be it is due to wxGTK 2.6.3?
Best wishes,
Michael
No, the some thing happens with 2.6.2 (I downgraded for testing but no luck....)
It's probably due to missing resources, try this (http://forums.next.codeblocks.org/index.php?topic=3001.msg23716#msg23716).
Hello,
If you are using autotools to build C::B, you can give a try to build C::B with the CodeBlocks-unix.cbp and ContribPlugins-unix.workspace (without forgetting to run ./update).
Best wishes,
Michael
I am building CB with a custom ebuild (from http://forums.gentoo.org/viewtopic-t-440412-highlight-codeblocks.html (http://forums.gentoo.org/viewtopic-t-440412-highlight-codeblocks.html) ).
Actually the ebuild executes the ./bootstrap, make, make install commands.
I tried, as artoj proposed, to insert the command "make clean-zipfiles" before execution of make, but the result is the same.
Anyway, after removing of libprojectwizard.{la,so} C::B working as expected.
I will make a build using .cbp and post the results, but I dont want to install anything in my system, without the package managment system.
Quote from: Slammer on April 29, 2006, 02:57:43 PM
execution fails with the message (before creation of main window):
"Something has gone wrong inside Code:Blocks and it will terminate.... blah blah"
No messages in console, only "Aborted"....
I'm using wxGTK 2.6.3 under Gentoo Linux.
Hi,
i had same problem: http://forums.next.codeblocks.org/index.php?topic=2976.0 (http://forums.next.codeblocks.org/index.php?topic=2976.0).
polygon7, we are using different compilers (I am using 3.4.6) but the failure is the same.