1
General (but related to Code::Blocks) / Re: Problems getting my printer to work with codeblocks.
« Last post by Miguel Gimenez on Today at 04:34:05 pm »May be related to ticket 1214, does you printing look like the PDF in the first post?
News:
The new Release 20.03 is out! You can download binaries for Windows and many major Linux distros here .
Recent Posts
2
General (but related to Code::Blocks) / Re: Console NOK from command prompt but OK from CB activation
« Last post by jmClifford on Today at 07:00:56 am »Hi. I found issue. I should have known better.
I was missing the last 3 dll's above. These are from the MinGW compiler section.
These I presume are what I need for standalone console operation while another 2 files (dll's) are required for wx_Widgets (Release and Debug versions of the same).
Regards JC......
Quote
C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug>dir
Volume in drive C is OS
Volume Serial Number is 5484-444A
Directory of C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug
09-May-24 02:47 PM <DIR> .
09-May-24 02:47 PM <DIR> ..
09-May-24 11:50 AM 74,745 Console.exe
09-May-24 11:01 AM 59,052 CreateUse.dll
09-May-24 02:47 PM <DIR> junk
09-May-24 11:04 AM <DIR> junk2
09-May-24 11:01 AM 2,384 libCreateUse.a
17-Oct-23 02:04 PM 112,640 libgcc_s_seh-1.dll
17-Oct-23 02:04 PM 2,282,496 libstdc++-6.dll
17-Oct-23 02:04 PM 54,784 libwinpthread-1.dll
6 File(s) 2,586,101 bytes
4 Dir(s) 148,848,451,584 bytes free
I was missing the last 3 dll's above. These are from the MinGW compiler section.
These I presume are what I need for standalone console operation while another 2 files (dll's) are required for wx_Widgets (Release and Debug versions of the same).
Regards JC......
3
General (but related to Code::Blocks) / Console NOK from command prompt but OK from CB activation
« Last post by jmClifford on Today at 04:08:49 am »Hi. I have a Win 10 system with CB. A project that uses a dll (compiled with another project) works fine when operated from CB (with the green arrow) but fails with a Command Prompt mode of operation.
The following gives some data from my system;
The NOK operation with the last bit of the above is a mystery ??
The OK operation atleast asked the operator for the required numbers.
Regards JC....
The following gives some data from my system;
Quote
The build =======>
g++.exe -Wall -fexceptions -g -c C:\u\CodeBlock_C++\DLL\02_Console\main.cpp -o obj\Debug\main.o
g++.exe -o bin\Debug\Console.exe obj\Debug\main.o C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug\libCreateUse.a
Output file is bin\Debug\Console.exe with size 72.99 KB
Process terminated with status 0 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
OK operation with green arrow (cb) =======>
a= 22
b= 11
the sum is 33
a= 44
b= 22
the difference is 22
NOK operation with Command Prompt ========>
C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug>dir
Volume in drive C is OS
Volume Serial Number is 5484-444A
Directory of C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug
08-May-24 02:59 PM <DIR> .
08-May-24 02:59 PM <DIR> ..
08-May-24 02:59 PM 74,745 Console.exe
08-May-24 02:15 PM 59,052 CreateUse.dll
08-May-24 02:15 PM 2,384 libCreateUse.a
3 File(s) 136,181 bytes
2 Dir(s) 148,093,124,608 bytes free
C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug>console.exe
C:\u\CodeBlock_C++\DLL\02_Console\bin\Debug>console.exe
The NOK operation with the last bit of the above is a mystery ??
The OK operation atleast asked the operator for the required numbers.
Regards JC....
4
General (but related to Code::Blocks) / Problems getting my printer to work with codeblocks.
« Last post by tonyaimer1 on Yesterday at 04:25:42 pm »Greetings all,
I am using C::B 20.03 on Linux Mint and all seems to work OK.
C::B gives a garbled mashup on my printer Kyocera 3550ci which is wirelesly connected to an old WinXP network.
I have been kindly helped to get my Samba file in line ( several years ago ) so that I can see my Windows network and can transfer files
between the windows XP network and my Linux Mint machine and vice versa.
I am beginning to think that the samba file may need to be modified somehow to allow C::B to print correctly.
It would be helpful to know if the samba file on this Linux machine is somehow causing the problem and perhaps I will need to get down
in the weeds to figure out what needs to be done. It would also be good to know if this is a known bug in C:B but
I doubt it.
I can print OK from LIbrewriter if I copy the program across but this may become problematic later as programs get bigger.
Librewriter on Linux prints my new docuemnts on the same printer perfectly.
I am also getting "wrong format" messages on my large format plotter ffom CAD packages on Linux which is also connected
to an XP machine which is also on the WinXP network if that is of any use.
Any ideas?
Regards
Tony Aimer
I am using C::B 20.03 on Linux Mint and all seems to work OK.
C::B gives a garbled mashup on my printer Kyocera 3550ci which is wirelesly connected to an old WinXP network.
I have been kindly helped to get my Samba file in line ( several years ago ) so that I can see my Windows network and can transfer files
between the windows XP network and my Linux Mint machine and vice versa.
I am beginning to think that the samba file may need to be modified somehow to allow C::B to print correctly.
It would be helpful to know if the samba file on this Linux machine is somehow causing the problem and perhaps I will need to get down
in the weeds to figure out what needs to be done. It would also be good to know if this is a known bug in C:B but
I doubt it.
I can print OK from LIbrewriter if I copy the program across but this may become problematic later as programs get bigger.
Librewriter on Linux prints my new docuemnts on the same printer perfectly.
I am also getting "wrong format" messages on my large format plotter ffom CAD packages on Linux which is also connected
to an XP machine which is also on the WinXP network if that is of any use.
Any ideas?
Regards
Tony Aimer
5
Help / Re: High CPU usage during build operation when verbose is enabled
« Last post by christo on May 06, 2024, 05:57:15 am »Thank you for the quick responses.
Issue is not only when there are lot of warnings, but also when there is lot of verbose. I use external makefile project, makefiles are generated by CMake with verbose enabled, which is in turn done by Yocto. Turning off verbose is not an option for me.
I think solution is to avoid as many regex matching as possible. Attaching a patch where a token string is added corresponding to each regex where possible in such a way that if the string is not present in the compiler output line, we can be sure that matching will fail.
So check if the token string is present in each line. If not present, don't do regex matching for that regex. If present, do matching as normal.
This significantly improved my build time. I think it will improve build time of normal CB projects projects as well. I've done only limited testing with this.
Issue is not only when there are lot of warnings, but also when there is lot of verbose. I use external makefile project, makefiles are generated by CMake with verbose enabled, which is in turn done by Yocto. Turning off verbose is not an option for me.
I think solution is to avoid as many regex matching as possible. Attaching a patch where a token string is added corresponding to each regex where possible in such a way that if the string is not present in the compiler output line, we can be sure that matching will fail.
So check if the token string is present in each line. If not present, don't do regex matching for that regex. If present, do matching as normal.
This significantly improved my build time. I think it will improve build time of normal CB projects projects as well. I've done only limited testing with this.
6
Help / Re: High CPU usage during build operation when verbose is enabled
« Last post by stahta01 on May 05, 2024, 07:00:38 pm »I would suggest disabling all the CB plugins you are not using or try selecting a different default compiler to see if any difference happens.
Edit: Also, change the project compiler and see if that helps.
Tim S.
Edit: Also, change the project compiler and see if that helps.
Tim S.
7
Help / Re: High CPU usage during build operation when verbose is enabled
« Last post by blauzahn on May 05, 2024, 05:26:43 pm »Some regex implementations are known to perform badly. For details see e.g:
see:
https://stackoverflow.com/questions/70583395/why-is-stdregex-notoriously-much-slower-than-other-regular-expression-librarie
https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2019/p1433r0.pdf
https://github.com/hanickadot
https://www.youtube.com/watch?v=7-aXp-u6008&ab_channel=NDCConferences
or search for slow c++ regex.
see:
https://stackoverflow.com/questions/70583395/why-is-stdregex-notoriously-much-slower-than-other-regular-expression-librarie
https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2019/p1433r0.pdf
https://github.com/hanickadot
https://www.youtube.com/watch?v=7-aXp-u6008&ab_channel=NDCConferences
or search for slow c++ regex.
8
Help / Re: High CPU usage during build operation when verbose is enabled
« Last post by ollydbg on May 05, 2024, 01:23:23 pm »I believe that there are a lot of codes to parse the compiler log message. So, if the compiler generate a lot of warnings, it takes a lot of time to parse those output.
So, sometimes, the building stage is really slow.
Not sure how to improve.
If I remember correctly, I have added some checks for the return line encoding, see this: The encoding text from GCC compiler should be UTF8 by default?
So, sometimes, the building stage is really slow.
Not sure how to improve.
If I remember correctly, I have added some checks for the return line encoding, see this: The encoding text from GCC compiler should be UTF8 by default?
9
Help / High CPU usage during build operation when verbose is enabled
« Last post by christo on May 05, 2024, 12:57:04 pm »Seeing high CPU usage by codeblocks, more than that of gcc, during compilation. I'm working external makefile project (makefile generated by cmake), and lot of verbose is enabled.
When analysed by perf, pcre2_match_32 is taking most of the CPU. Cause is that each of the build log line is check against 34 regular expressions.
I'm not much familiar with regex, but can anything to be done to improve the performance here?
When analysed by perf, pcre2_match_32 is taking most of the CPU. Cause is that each of the build log line is check against 34 regular expressions.
I'm not much familiar with regex, but can anything to be done to improve the performance here?
10
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by Wkerry on May 05, 2024, 11:07:02 am »Anyone got any updates on the https://sourceforge.net/p/codeblocks/tickets/663/ ticket patch status?