1
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by danselmi on Today at 09:23:53 pm »As promised
Find attached the previously mentioned patch.
Find attached the previously mentioned patch.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
2
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by blauzahn on Today at 01:58:16 pm »As mentioned in the ticket: If C++17 is an acceptable lower limit, the std::filesystem will become available. If it provides the needed functionality to replace libgamin in cb, I would prefer std over wxWidgets. Since I have not used neither std::filesystem nor wxFilesystemwatcher yet, I can not say. At least it has a non-member function named .
Code
last_write_time3
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by Wkerry on Today at 09:52:50 am »See https://sourceforge.net/p/codeblocks/tickets/663/ for "Don't use deprecated gamin library", which may be helpful.
4
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by blauzahn on Yesterday at 05:49:01 pm »@danselmi: Great!
5
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by danselmi on Yesterday at 04:59:22 pm »Fedora also don't provide gaming anymore.
I have a patch relying on wxFilesystemwatcher. This I have tested on windows and feodra39.
Will provide it later tonight when I have access to my computer.
I have a patch relying on wxFilesystemwatcher. This I have tested on windows and feodra39.
Will provide it later tonight when I have access to my computer.
6
Announcements / Re: successor of 20.03 available?
« Last post by grem on April 27, 2024, 07:00:01 pm »main focus is on stabilizing the clangd plug-in.Is it planning to prepare "Nightlies" tarballs under https://sourceforge.net/projects/codeblocks/files/Sources/ to simplify packaging developer preview versions in Linux distributives?
And fix regressions in the before hidden glob feature.
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.
7
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by blauzahn on April 27, 2024, 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.
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.
8
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by killerbot on April 27, 2024, 05:16:54 pm »ubuntu 24.04 no longer provides that package ?
9
Using Code::Blocks / Use of Open Watcom Compiler on Linux (Mint Victoria 20.3)
« Last post by ThierryD on April 27, 2024, 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.
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.
10
Nightly builds / Re: The 27 April 2024 build (13513) is out.
« Last post by Xaviou on April 27, 2024, 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 :
Regards
Xav'
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-devRegards
Xav'