11
Help / AVR Compiler
« Last post by ksoni on March 15, 2025, 11:14:19 am »How to set / add avr compiler in codeblocks 20:03, 64 bit version
News:
The new Release 20.03 is out! You can download binaries for Windows and many major Linux distros here .
Recent Posts
12
Development / Re: cannot find -luser32 etc.
« Last post by reckless on March 15, 2025, 09:08:03 am »you can use allmost whatever compiler you like borland msvc mingw watcom etc.
the thing to look out for is if you are not familar with the compiler you chose to use as they all use different flags for the same operation.
for msys2 you can download the codeblocks package via pacman but if you want to use the 32 bit mingw compiler you need to do a bit of compiler setup since it defaults to 64 bit mingw.
borland atleast the older free version defaults to 32 bit so should be easy enough.
msvc has it's own ide so using codeblocks with it is more user preference.
watcom also comes with an ide but it lacks quite a few features like syntax highlighting.
TDM-mingw has both 32 and 64 bit mingw compilers (in one package even) and was shipped with older versions of codeblocks.
the problem with TDM is that it was discontinued somewhere around gcc 10 so it lacks some of the more modern standards.
it was also a bit buggy at times.
as for where to get them use google or startpage or whatever search engine you fancy.
the thing to look out for is if you are not familar with the compiler you chose to use as they all use different flags for the same operation.
for msys2 you can download the codeblocks package via pacman but if you want to use the 32 bit mingw compiler you need to do a bit of compiler setup since it defaults to 64 bit mingw.
borland atleast the older free version defaults to 32 bit so should be easy enough.
msvc has it's own ide so using codeblocks with it is more user preference.
watcom also comes with an ide but it lacks quite a few features like syntax highlighting.
TDM-mingw has both 32 and 64 bit mingw compilers (in one package even) and was shipped with older versions of codeblocks.
the problem with TDM is that it was discontinued somewhere around gcc 10 so it lacks some of the more modern standards.
it was also a bit buggy at times.
as for where to get them use google or startpage or whatever search engine you fancy.
13
Development / Re: asm("int3"); /*trap*/ query
« Last post by reckless on March 15, 2025, 08:54:02 am »Code
#if defined(__i386__) || defined(__x86_64__)
__asm__ __volatile__("int {$}3":);
#elif defined(__arm__)
__asm__ __volatile__("udf #0xfe");
#elif defined(__aarch64__)
__asm__ __volatile__("brk #0xf000");
#else
__asm__ __volatile__("unimplemented");
#endifthis should cover it if you need it again.
14
General (but related to Code::Blocks) / Re: patch for the autotools build to work with Msys2/MinGW32
« Last post by reckless on March 15, 2025, 08:38:48 am »i might be able to post an ucrt32 version for interrested parties soon as i completed building the ucrt32 cross compiler on msys2.
might be interresting for people still using 32 bit vista or win7 though they need to download the ucrt update for there OS (avaliable from microsoft).
also experimenting with a TDM based version of gcc-14.2.0 ucrt with a lot of bugfixes to the code.
the mingw* msvcrt version works quite fine allready except in gdk-pixbuf and ogre3d but even the non TDM version bugs out on those two if linked to the static runtimes so it seems to be a bug in there code.
for some reason gdk-pixbuf links in the static version of the image loaders when linked to the static runtimes but not when doing a normal build which has me a bit miffed.
might be interresting for people still using 32 bit vista or win7 though they need to download the ucrt update for there OS (avaliable from microsoft).
also experimenting with a TDM based version of gcc-14.2.0 ucrt with a lot of bugfixes to the code.
the mingw* msvcrt version works quite fine allready except in gdk-pixbuf and ogre3d but even the non TDM version bugs out on those two if linked to the static runtimes so it seems to be a bug in there code.
for some reason gdk-pixbuf links in the static version of the image loaders when linked to the static runtimes but not when doing a normal build which has me a bit miffed.
15
General (but related to Code::Blocks) / Re: Will there be a 32-bit (i686) version of Code::Blocks 24.12?
« Last post by reckless on March 15, 2025, 08:26:55 am »well i can provide you with a 32 bit build of it but it is intended for Msys2 Mingw32 so might have a lot of dependant dll's that need copying off.
its in PKGBUILD format but you can open the package with 7zip and just copy the whole thing to wherever you need it.
its in PKGBUILD format but you can open the package with 7zip and just copy the whole thing to wherever you need it.
16
Help / Re: Installing Code::Blocks from source on Linux
« Last post by cacb on March 14, 2025, 09:17:01 pm »For building Code::Blocks from source under Kubuntu use build_cb.sh found at
https://gitlab.com/arnholm/cpde_3rdparty/-/tree/master/gcc/codeblocks
Maybe it is helpful to some.
https://gitlab.com/arnholm/cpde_3rdparty/-/tree/master/gcc/codeblocks
Maybe it is helpful to some.
17
Announcements / Re: New alias
« Last post by LETARTARE2 on March 14, 2025, 03:21:28 pm »Except for the first message I could write, I still can't write a message with a joins file.
on this new account.
This should help the site administrator
on this new account.
This should help the site administrator
18
Announcements / New alias
« Last post by LETARTARE2 on March 14, 2025, 03:02:41 pm »My old 'LETARTARE' account no longer allowing you to create messages, I created a new 'LETARTARE2' account to do a test
19
Help / Re: Installing Code::Blocks from source on Linux
« Last post by LETARTARE on March 14, 2025, 01:51:30 pm »With 'Leap-15.6' we have the two versions which seem to coexist : 'libtiff.so.5' and 'libtiff.so.6'
20
Help / Re: Stripping debug info from output tree
« Last post by everSome on March 13, 2025, 06:43:48 pm »I'm being rather forgetful about this stuff as I did it a year or two ago. You'll notice that at the bottom of the update32_64_MSYS2.sh file there is a reference to
update32_64_MSYS2.shYou can just delete it, or I could post it if you'd find it useful. I've only used this in the UCRT64 and MINGW64 environments. What that python script does is examine the import tables of all .exe and .dll files in output32_64 in a repetative manner for references to MSYS2 .dll files and copies them into output32_64.