H,
I have 2 linux installations of Code::Blocks (from Jens Lody repository)
Pc A: svn 6703
Pc B: svn 6718
My setup relies on using Code::Blocks environment variables defined via Settings->Environment->Environment Variables
This works fine in Code::Blocks svn 6703, but in svn 6718 the option Environment Variables is completely non-existent...!
Why is that? Is it a bug? I hope so...
I use svn r6718 from my repo and "Environment Variables" is still there.
cacb, do you have the envvar plugin installed and enabled? (Plugins -> Manage)
Quote from: oBFusCATed on October 22, 2010, 08:51:35 AM
cacb, do you have the envvar plugin installed and enabled? (Plugins -> Manage)
If it is also not there, make sure you have the
codeblocks-contrib package installed.
Quote from: jens on October 22, 2010, 11:58:10 AM
Quote from: oBFusCATed on October 22, 2010, 08:51:35 AM
cacb, do you have the envvar plugin installed and enabled? (Plugins -> Manage)
If it is also not there, make sure you have the codeblocks-contrib package installed.
Ok, thanks a lot, that solved it! I just had to do a
$sudo apt-get install codeblocks-contrib and the environment variables option was back where it used to be. :D
This happened after I installed Kubuntu 10.10 from scratch + plus codeblocks etc. Somehow the
codeblocks-contrib was not included.
Thanks again, much appreciated :D
Quote from: cacb on October 22, 2010, 05:39:30 PM
Thanks again, much appreciated :D
However..... After upgrading to svn 6470, some of my projects are now crashing Code::Blocks when I try to open a workspace or project file. I have confirmed the behaviour on 2 Kubuntu machines (10.04 and 10.10), crash dump attached.
Any advice appreciated.
UPDATE: I found out what caused the crash
My projects are cross platform, using msvc8 compiler on windows and gcc on linux. My projects had a setting like shown below on the project level (
not under any of the 4 build targets i have: W32_Debug, W32_Release, UX_Debug, UX_Release
<Option compiler="msvc8" />Removing this with a text editor fixed the crash issue. However, this used to not cause any crash before, so it looks like a bug to me.