User forums > Using Code::Blocks
Error "assert.h: missing binary operator" when creating/compiling new projects
ascii_moe:
Still the same:
wx-config --list
Default config is gtk2-ansi-release-2.8
Default config will be used for output
What should the output be now?
ascii_moe:
Hi Jens,
it looks like I solved this issue (even if I don't know what the reason for this fault was):
I simply removed the current Code::Blocks installation and reinstalled it.
Now everything works fine, again!
In detail, that's what I did:
1. Check the currently installed packages:
$ dpkg -l | grep blocks
ii codeblocks 8.02 Code::Blocks integrated development environm
ii codeblocks-contrib 8.02 Contrib plugins for Code::Blocks IDE
ii codeblocks-dbg 8.02 Code::Blocks debugging libraries
ii codeblocks-dev 8.02 Code::Blocks development files (SDK)
ii libcodeblocks0 8.02 Code::Blocks shared library
2. Remove this packages:
$ sudo apt-get remove codeblocks (This removes codeblocks, codeblocks-contrib and codeblocks-dbg.)
$ sudo apt-get remove codeblocks-dev
$ sudo apt-get remove libcodeblocks0
3. Check again:
$ dpkg -l | grep blocks
rc codeblocks 8.02 Code::Blocks integrated development environm
rc libcodeblocks0 8.02 Code::Blocks shared library
4. Purge remaining packages:
$ sudo dpkg --purge codeblocks
$ sudo dpkg --purge libcodeblocks0
5. Deleting the ".codeblocks" directory in my home directory:
$ rm -rf ~/.codeblocks
6. Reinstall all *.deb packages:
codeblocks_8.02_amd64.deb
codeblocks-contrib_8.02_amd64.deb
codeblocks-dbg_8.02_amd64.deb
codeblocks-dev_8.02_amd64.deb
libcodeblocks0_8.02_amd64.deb
libwxsmithlib0_8.02_amd64.deb
libwxsmithlib0-dev_8.02_amd64.deb
$ sudo dpkg -i *deb
7. Check the reinstalled packages:
$ dpkg -l | grep blocks
ii codeblocks 8.02 Code::Blocks integrated development environm
ii codeblocks-contrib 8.02 Contrib plugins for Code::Blocks IDE
ii codeblocks-dbg 8.02 Code::Blocks debugging libraries
ii codeblocks-dev 8.02 Code::Blocks development files (SDK)
ii libcodeblocks0 8.02 Code::Blocks shared library
That's it!
Since then everything went back to normal (creating and compiling new projects, compiling old projects, etc.).
I really don't know what caused this strange behaviour before. Maybe some config file(s) of the old installation have been corrupted?
Nonetheless, many thanks for your help! (I hope that this fault won't occur again... ;-) )
Regards,
Thomas
Jenna:
Most likely you had wrong settings in the global compiler settings under "Settings -> Compiler and debugger -> Global compiler settings".
These settings are stored in C::B's main conf-file and can mess up your projects.
In this place only settings that really (really !!) should belong to each and any project of the specified compiler should be made.
ascii_moe:
Can you tell me which one the main config file is? I could not find it, yet.
Maybe it would help, only to delete/reset this file and start with a new configuration, instead of a reinstallation?
Jenna:
--- Quote from: ascii_moe on May 27, 2010, 08:03:16 am ---Can you tell me which one the main config file is? I could not find it, yet.
Maybe it would help, only to delete/reset this file and start with a new configuration, instead of a reinstallation?
--- End quote ---
~/.codeblocks/default.conf
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version