User forums > Using Code::Blocks

Strange wxSmith behaviour

<< < (2/3) > >>

stahta01:
After editing the project to use wxWidgets 3.0 Shared Monolib I did NOT see the problem.

Tested with WXWIN_COMPATIBILITY_2_8=1 and WXWIN_COMPATIBILITY_2_6=0.

Tim S.

stahta01:
OP is making a major wxWidgets/CB mistake.
In places he has shared wxWidgets and in others he has static wxWidgets.
Note: This would likely NOT cause the compile error he is seeing.

Tim S.

stahta01:
I recommend the OP delete the PCH file/folder (wx_pch.h.gch) and rebuild the project and see if the error goes away.
If it does NOT post the full build log of the reduced CB project.

Edit: I forgot it is a runtime and NOT a build error; therefore the mix of static/shared might cause the issue.
I tested for a runtime error and I got one; now to see if the OP fix makes the problem go away.

Tim S.

stahta01:
The run-time error went away after I commented out the two lines the OP suggested.

I will check over the project I created and upload it for an wxSmith person to try.
NOTE: The OP did NOT include the "wxsmith\IsolatingErrorframe.wxs" file that I would guess will be needed.

Tim S.

stahta01:
Attached new zipped edited project containing an wxWidgets 2.8 cbp file.
Edit: The wxWidgets 2.8 does NOT have the same crash on running the project; so, likely problem is a change caused by wxWidgets 3.0.

Added use of CB Global var wx30; changed to monolib and DLL wxWidgets build.
Removed the compiler of the PCH to save time for the wxSmith/CB Dev that looks at the problem.

Edit: Remember it is a run-time error and NOT an compile/link error; I forgot that, sorry about that.

Tim S.

Navigation

[0] Message Index

[#] Next page

[*] Previous page