Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
Using Code::Blocks / Re: Code::Blocks randomly crashing
« Last post by BlueHazzard on February 14, 2019, 04:50:27 pm »
What encoding are you using for your files?
Did the spell checker plugin worked if you had it active?
Have you installed some dictionary?
Nightly builds / Re: The 09 February 2019 build (11562) is out.
« Last post by BlueHazzard on February 14, 2019, 04:46:22 pm »

In the present version, the last letter is occasionally underlined in red. When choosing a language, sometimes a serious error in CB also occurs.

I am sure that there is a similar problem for all languages with 8-bit encoding: Russian, Greek, Hebrew, Arabic and all others too.

please give us an example file....

It seems that no one here uses a other encoding, so we need an example file from your side....
What happens if you switch encoding to UTF8?
Using Code::Blocks / Re: wxsmith plugin, where is it?
« Last post by BlueHazzard on February 14, 2019, 04:44:08 pm »
I am fascinated how many problems your have xD, and more that you still stick to it! My compliment for your endurance!
for me it was always more or less a configure and make....

Have you installed libhunspell via packet manager or by compiling by yourself?
General (but related to Code::Blocks) / Re: __attribute__ Not Recognized
« Last post by BlueHazzard on February 14, 2019, 04:40:09 pm »
beside this being the wrong place to ask this kind of question i do not think that the compiler does not understand the __attribute__ bit, but the bit before the __attribute__ part.... There is some class as return value that is not defined or declared...

This project is migrated from Windows 7 because I need Valgrind. This project was transferred from Windows 7 to Ubuntu. I suspect that is trouble. I have created a new project in Ubuntu, and transferred all the files into the new project. But this did not solve the compilation problem I opened this thread for.
Of course you can not use the same project.... there are tons of defines in the windows project file that are not supported or wrong on linux.
If you have a compiling problem follow this faq:
Using Code::Blocks / Re: wxsmith plugin, where is it?
« Last post by jjenson on February 14, 2019, 04:12:46 pm »
I deleted a bunch of empty file trees and ran the command again; didn't realize that empty directories would interfere with a build. This time it started building packages.

It built:


then I get:

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/ (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/
Hint: check if the library actually comes from a package.

and finally:

recipe for target 'binary-predeb-IMPL/codeblocks-contrib' failed
make: *** [binary-predeb-IMPL/codeblocks-contrib] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2

I'm getting so close! Anyone know what I can try next to alleviate the problem?
Add readline.c to the targets Release and Debug

Select readline.c file
File Properties
Tab: Build

Tim S.
Post the full rebuild in code tags.
And, make sure the second file is part of the project.

Tim S.


Make sure you are using an CB Project. If yes, post the full rebuild log.

Tim S.
Hi, Tim,
I use the CB project, and the full rebuild log as the picture 2 illustrated.
I upload the whole project (test.rar) in the attachment.
Thank you.
P.S. My CB is codeblocks-17.12mingw-setup.exe
Using Code::Blocks / Re: Specific highlighting
« Last post by Phumus-9 on February 14, 2019, 02:20:13 pm »
Moreover I noticed that the text I write in C::B is not sharp. I don't know how to explain, but it is kind of blurred. I use the default font.
OS, Monitor DPI, scaling setting, C::B version? If you're on windows you have to tell codeblocks that it is dpiaware or something similar. Or try a night build.

Windows 10, the screen is 17' and full HD (1920x1080), scaling setting in Windows settings menu is 125%, C::B 17.12.
I right clicked on C::B icon -> Properties -> Compatibility. There I enabled "Disable full screen optimization". Then in the same menu I clicked "Modify high DPI settings" and there I enabled the first opion and selected "Use DPI values at the opening of this program". Then I applied these new settings, opened the program but nothing changed.

You talked about an hack, do you have a link where I can elaborate on this?
I think it is on by default, but is somewhere in the editor settings.
Mhh, I snooped a bit in Settings -> Editor, but I found nothing.

Thanks again!
Pages: 1 2 3 [4] 5 6 7 8 9 10