Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
Using Code::Blocks / Re: stack size
« Last post by matthen on June 03, 2021, 06:11:58 pm »
Hello,
I am trying to increase the stack size
I write in the linker options "-Wl,--stack,2048" but I receive an error unrecognized option '--stack'
Could anyone help?.

The string "-Wl,--stack=2048" worked for me. Also, I believe that the units are bytes, rather than megabytes, so it's probably sensible to add a few 0s. (Happy to be proven wrong)
92
Contributions to C::B / Re: Updating wxWidgets project wizard
« Last post by cacb on June 03, 2021, 05:44:14 pm »
The wizard supports the following compilers: Open Watcom, Borland C++, MSVC, and GCC. IMO OW and BCC are dead and I do not think MSVC is used much with C::B.

It may be that MSVC is not very common with C::B, but I have used that combination for many years and still do.
93
Help / Re: mingw missing libs
« Last post by Denis Mungle on June 03, 2021, 05:15:00 pm »
Thx its working now :) !!
94
Help / Re: mingw missing libs
« Last post by stahta01 on June 03, 2021, 05:06:17 pm »
Rename or delete the folder "C:\MinGW"!
Having this folder messes up the CB auto-detect and makes some other MinGW GCC compilers  not work right.
Edit: Other folders that are bad to have include "C:\MinGW32" or "C:\MinGW64".

You then need to set your CB compiler settings to use the MSys2 MinGW64 toolchain.
You need to decide if you wish to use 64 or 32 bit MinGW libraries.
Then you can try to use the MSys2 MinGW64 libraries.

Tim S.
95
Help / Re: mingw missing libs
« Last post by Denis Mungle on June 03, 2021, 04:56:35 pm »
Here are my MinGW and CB project .zip , i still cant understand why the -ldwmapi lib cant be found. The compiler settings and linker settings are still the same as i previously said, the compiler installation dir is the auto-detected C:\MinGW. Do i have to add a full path to the lib?

Also when i write in the command line pkg-config --libs gtk+-3.0
-LC:/msys64/mingw64/bin/../lib -lgtk-3 -lgdk-3 -lz -lgdi32 -limm32 -lshell32 -lole32 -Wl,-luuid -lwinmm -ldwmapi -lsetupapi -lcfgmgr32 -lpangowin32-1.0 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lintl

It shows the right lib, but i dont know how to access that directory.
Thx
96
Contributions to C::B / Re: Updating wxWidgets project wizard
« Last post by ollydbg on June 03, 2021, 12:20:08 pm »
Do you really want the wizard to be tied to one wxWidgets distribution and being incompatible with self-built and official binaries?
No, I think by using eranif/wx-config-msys2 tool, config wx project may be simple. I mean I can only create a simple console project, and tweak the include search path, lib search path and libs by using the shell escape command.

The expect way could let our wxWidgets wizard also support msys2's prebuild libraries.
97
Contributions to C::B / Re: Updating wxWidgets project wizard
« Last post by PB on June 03, 2021, 10:57:05 am »
eranif/wx-config-msys2: wx-config tool for MSYS2 based installation of wxWidgets using the mingw64 repository
I recently found this good tool, and Code::Blocks support shell escape in the include search or lib search options, so using this could be simple. I haven't tried this tool yet.

Sorry, I do not understand the relevance.

The wizard supports the following compilers: Open Watcom, Borland C++, MSVC, and GCC. IMO OW and BCC are dead and I do not think MSVC is used much with C::B.

Still, MSYS2 is but one GCC-based MSW distribution. wxWidgets developers suggest that on MSW, you should build wxWidgets by yourself which allows you also to tailor the build to your needs.

Please notice that when using MSYS2 prebuilt package:
1) The library file (and folder?) names are different than those of official wxWidgets binaries or the binaries self-built with GCC makefile (and in future CMake file).
2) AFAIK, the MSYS2 package does not contain the new Edge-based wxWebView, leaving you with the obsolete IE-based one. AFAICT, configure does not even support Edge backend.
3) Of course, you are at mercy of packagers, which wxWidgets versions do they offer and with which options (e.g., for some reason, some people seem to favour the monolithic build).

Do you really want the wizard to be tied to one wxWidgets distribution and being incompatible with self-built and official binaries?
98
Contributions to C::B / Re: Updating wxWidgets project wizard
« Last post by PB on June 03, 2021, 10:44:30 am »
This may be off topic, but be aware on Windows the three main GCC compilers collections/systems are:
1) MSYS2
2) MingW64
3) Cygwin

The MSYS2 and Mingw64 when you start to use them are different and if you try to mix the libraries causes issues. If you do install them on the one PC then based on my experience they will interfere with one another due to search path issues, so I rename the directories when swapping between the three.

I must have at least 10 GCC-based compiler toolchains installed, from three different "distributions" (mingw-w64, MSYS2, TDM). I have never encountered any issue but of course, I did not add any of them to the PATH.
99
Nightly builds / Re: The 24 May 2021 build (12452) is out.
« Last post by oBFusCATed on June 03, 2021, 10:04:47 am »
So, is there any problem or not?
100
General (but related to Code::Blocks) / Re: CodeBlocks Msys2 and wxWidgets
« Last post by ollydbg on June 03, 2021, 08:06:43 am »
If you are just doing shared it is normal to use "wx_$(WX_TOOLKIT)$(WX_SUFFIX)_aui-$(WX_VERSION)" instead of "libwx_$(WX_TOOLKIT)$(WX_SUFFIX)_aui-$(WX_VERSION).a".

Tim S.
Hi, thanks for the help, indeed, I just test it, the cbp can be simplified as:

Code
		<Linker>
<Add option="-mthreads" />
<Add library="wx_base$(WX_SUFFIX)-$(WX_VERSION)" />
<Add library="wx_base$(WX_SUFFIX)_xml-$(WX_VERSION)" />
<Add library="wx_base$(WX_SUFFIX)_net-$(WX_VERSION)" />
<Add library="wx_$(WX_TOOLKIT)$(WX_SUFFIX)_core-$(WX_VERSION)" />
<Add library="wx_$(WX_TOOLKIT)$(WX_SUFFIX)_adv-$(WX_VERSION)" />
<Add library="wx_$(WX_TOOLKIT)$(WX_SUFFIX)_aui-$(WX_VERSION)" />
<Add library="opencv_imgproc$(CV_VERSION)" />
<Add library="opencv_core$(CV_VERSION)" />
<Add library="opencv_imgcodecs$(CV_VERSION)" />
<Add library="opencv_calib3d$(CV_VERSION)" />
<Add library="opencv_videoio$(CV_VERSION)" />
<Add directory="$(TARGET_COMPILER_DIR)lib" />
<Add directory="$(TARGET_COMPILER_DIR)bin" />
</Linker>
Pages: 1 ... 5 6 7 8 9 [10]