Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Announcements / Re: successor of 20.03 available?
« Last post by grem on Yesterday at 07:00:01 pm »
Quote from: killerbot on Yesterday at 08:11:57 am
main focus is on stabilizing the clangd plug-in.

And fix regressions in the before hidden glob feature.
Is it planning to prepare "Nightlies" tarballs under https://sourceforge.net/projects/codeblocks/files/Sources/ to simplify packaging developer preview versions in Linux distributives?
Unfortunately the zip archives that generated by Sourceforge on request are temporary and URLs lifetime seems lesser than 24 hours. If request it again the zip-file has differ checksum.
2
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by blauzahn on Yesterday at 06:59:28 pm »
looks like.

On arch I installed it from trunk but it seems that the source I used then (https://people.gnome.org/~veillard/gamin/) is no longer available.
3
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by killerbot on Yesterday at 05:16:54 pm »
ubuntu 24.04 no longer provides that package ?
4
Using Code::Blocks / Use of Open Watcom Compiler on Linux (Mint Victoria 20.3)
« Last post by ThierryD on Yesterday at 04:23:12 pm »
Hi,

I continue to test this compiler on Linux. It seems "enougth stable" same with V2 always in work on GitHub : https://github.com/open-watcom/open-watcom-v2/releases/tag/Current-build
I install last "stable build" with sample command : "sudo ./open-watcom-2_0-c-linux-x64".
Result : directory installation in /usr/bin/watcom (under this directory many sub-directories, only "binl" or "binl64" used directly on Linux, version 32 bits or 64 bits of tools)
After tests (without CB, because syntax are not recognize ...) results are :
  construct OK with two lines, compilation and then linkage (initial PATH : "export PATH=/usr/bin/watcom/binl:$PATH")
         wcc386 hello.c -ecc -bt=linux -i=/usr/bin/watcom/lh -d2 -dDEBUG -d_DEBUG -fo=objOW32/Debug/hello.o
         wlink debug watcom file objOW32/Debug/hello.o name binOW32/Debug/hello.exe  form ELF run LIN LIBP /usr/bin/watcom/lib386/linux LIBP /usr/bin/watcom/lib386
  construct OK with two lines, compilation and then linkage (after change $PATH : "export PATH=/usr/bin/watcom/binl64:$PATH") :
        wcc386 hello.c -ecc -bt=linux -i=/usr/bin/watcom/lh -d2 -dDEBUG -d_DEBUG -fo=objOW64/Debug/hello.o
        wlink debug watcom file objOW64/Debug/hello.o name binOW64/Debug/hello.exe form ELF run LIN LIBP /usr/bin/watcom/lib386/linux LIBP /usr/bin/watcom/lib386
  construct OK with two lines, compilation and then linkage (initial PATH : "export PATH=/usr/bin/watcom/binl:$PATH")
        wcc386 hello.c -ecc -bt=linux -i=/usr/bin/watcom/lh -d0 -dNDEBUG -fo=objOW32/Release/hello.o
        wlink file objOW32/Release/hello.o name binOW32/Release/hello.exe  form ELF run LIN LIBP /usr/bin/watcom/lib386/linux LIBP /usr/bin/watcom/lib386
  construct OK with two lines, compilation and then linkage (after change $PATH : "export PATH=/usr/bin/watcom/binl64:$PATH") :
         wcc386 hello.c -ecc -bt=linux -i=/usr/bin/watcom/lh -d0 -dNDEBUG -fo=objOW64/Release/hello.o
        wlink file objOW64/Release/hello.o name binOW64/Release/hello.exe  form ELF run LIN LIBP /usr/bin/watcom/lib386/linux LIBP /usr/bin/watcom/lib386
 
WARNING : Open Watcom compiler don't generate 64 bits ELF on Linux, same with use of directory /usr/bin/watcom/binl64 in PATH.
  That is irrelevant, and compromize use of version 64 bits of these compiler. Nothing interest to test 64 bits ... same behavior on Windows system !!!

NB : Option "-ecc" during compilation, because by default OW use  special calling convention (__watcall), then "-ecc" force calling convention to __cdecl most compatible.

Syntax and list of options of these two commands in joined files.

Is it difficult to integrate OW into CB on Linux (by discover during first run by example) ?

Thank's

Thierry D.
5
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by Xaviou on Yesterday at 11:58:04 am »
Hi.

OS X version of this rev can be downloaded from my website.
There is only a macOS-11.6 version.
Note that it is not a notarized version of the application.

32 bits version for Windows can also be found in the same place.

Debian Bookworm and Bullseye (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04 and 23.10 versions can be installed from my ppa

Ubuntu-24.04 failed to build :
Code
Missing build dependencies: libgamin-dev

Regards
Xav'
6
Nightly builds / The 27 April 2024 build (13513) is out.
« Last post by killerbot on Yesterday at 08:12:39 am »
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 27 April 2024 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2024/CB_20240427_rev13513_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

  • Clangd_client: 1.2.119 24/04/4 Apply Christo warning/error diagnostic msgBox patch (with mods). Thanks Christo
  • mark project workspace to be 32 bit
  • avoid compiler warnings by not using folder not present anymore
  • always update ZIP file (in case resources change)
  • check for nullptr of info window data (layoots/perspectives)
  • applied patch #1470: Make FileSystemWatcher interface optional
  • Clangd_client: 1.2.121 24/04/21 Fix to avoid json throw 302
  • Build: Fix building with autotools after r13437
  • Clangd_client: 1.2.122 24/04/26 Fix stall in "Show call tip" when using clangd Hover request

Regressions/Confirmed/Annoying/Common bugs:


    7
    Announcements / Re: successor of 20.03 available?
    « Last post by killerbot on Yesterday at 08:11:57 am »
    main focus is on stabilizing the clangd plug-in.

    And fix regressions in the before hidden glob feature.
    8
    Help / wxSmith adds the event handler, but the connection is lost immediately
    « Last post by ollydbg on April 26, 2024, 04:48:05 pm »
    I see some strange issue about using wxSmith to add some event handler.

    Suppose I have a wxButton on the GUI designer, and when I go to the left navigation panel of the wxSmith, to add a new event handler.

    It looks like the event handler function is added to the associated header files and implementation file, that's good, but I soon noticed that the connection between the gui control and the event handler is lost.

    What I need to do is the use the mouse to click on other wxSmith control again, and click back on the previous control again, and in the wxSmith's Events panel, I have to open the list box of the event functions, and select the one I recently added. By doing this, the actual connection between the gui control and event handler is generated, and I see there is a function call statement like:

    Code
    Connect(ID_CHECKBOX1, wxEVT_COMMAND_CHECKBOX_CLICKED, (wxObjectEventFunction)&MyDialog::OnCheckBoxClick);

    is added.

    My question is: do you see the same issue here? I mean why I need some extra steps to bind the control and event handler? It should bind in the first step when I add the event handler.

    Thanks.

    9
    Announcements / Re: successor of 20.03 available?
    « Last post by christo on April 26, 2024, 04:49:35 am »
    Hi devs, a new release is a good idea since LSP support is added. Now it is not easy to recommend codeblocks to others as most of them gets uninterested when I say they have to use nightly builds
    10
    Announcements / Re: successor of 20.03 available?
    « Last post by blauzahn on April 24, 2024, 12:36:14 pm »
    I am no cb dev. So, it is personal speak. I use the current trunk anyway. Nonetheless, I assume that it will serve as the next release somewhen.
    Pages: [1] 2 3 4 5 6 ... 10