Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
Pardon my ignorance

what is scintilla?

what is MSW?

Tony
92
It is not driver-related, just Scintilla failing to print outside MSW.
93
Yes it does look a bit like that.  I had thought of a third option to resolving the problem

I could buy a new printer ( A4 ) and plug it directly into the Linux box and see if the problem goes away or
persists. This would eliminate the samba issue and might be driver related?

Tony.
94
Nightly builds / The 09 May 2024 build (13518) is out.
« Last post by killerbot on May 09, 2024, 04:58:42 pm »
We switched to gcc 13.1.0 (on 04 June 2023) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/13.1.0-16.0.5-11.0.0-ucrt-r5/winlibs-x86_64-posix-seh-gcc-13.1.0-mingw-w64ucrt-11.0.0-r5.7z

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx324_2D_gcc1310-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls13.1.0.7z


The 09 May 2024 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2024/CB_20240509_rev13518_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

  • applied patch by danselmi from ticket #663: Don't use deprecated gamin library

Regressions/Confirmed/Annoying/Common bugs:


    95
    May be related to ticket 1214, does you printing look like the PDF in the first post?
    96
    Hi. I found issue. I should have known better.
    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......
    97
    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;

    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....
    98
    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 
    99
    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.
    100
    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.
    Pages: 1 ... 5 6 7 8 9 [10]