Recent Posts

Pages: 1 [2] 3 4 5 6 7 ... 10
11
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.
12
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.
13
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.
14
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
15
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
16
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'
17
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.sh
You 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.
18
Help / Re: Stripping debug info from output tree
« Last post by everSome on March 13, 2025, 04:42:38 pm »
I forgot to mention that as I've commented out stripping since don't want to do that, you'll have to uncomment the three strip commands around lines 241 to 243.
REM echo Stripping debug info from output tree
REM %3 "%CB_OUTPUT_DIR%/*.exe"
REM %3 "%CB_OUTPUT_DIR%/*.dll"
REM %3 "%CB_OUTPUT_RESDIR_STRIP%/plugins/*.dll"

Just remove the "REM "prefix threof.
19
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Miguel Gimenez on March 13, 2025, 01:38:03 pm »
Probably copying libtiff.so.6 to libtiff.so.5 is enough, but I would ask in the wxWidgets' forum.
20
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Krice on March 13, 2025, 11:18:01 am »
Libtiff is in usr/lib64 but it has libtiff.so, libtiff.so.6 and libtiff.so.6.0.2. Do I need version 5 or what. Linux library stuff is so confusing.
Pages: 1 [2] 3 4 5 6 7 ... 10