Author Topic: wxWidgets 2.9.1 Development Release  (Read 6227 times)

Offline ptDev

  • Almost regular
  • **
  • Posts: 222
wxWidgets 2.9.1 Development Release
« on: July 19, 2010, 10:33:35 pm »
wxWidgets 2.9.1 is now officially available for download.

Grab it here. :)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5218
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: wxWidgets 2.9.1 Development Release
« Reply #1 on: July 20, 2010, 02:22:06 am »


Quote
Note about naming: while 2.9.1 is called a "development" release,
this only means that API is not guaranteed to remain unchanged in
the subsequent 2.9.x releases, unlike in the stable 2.8.x branch. We
believe the current version is stable and suitable for use in
production environment and recommend using it for any new projects
using wxWidgets.


We are especially looking forward to your feedback about the changes
in this release compared to 2.8 version if you're upgrading. Please
let us know about any regressions (http://trac.wxwidgets.org/newticket)
so that we could fix them in the upcoming 3.0. Thanks in advance!

So, the author of wx recommend we do a upgrade to 2.9.1?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11716
    • Travis build status
Re: wxWidgets 2.9.1 Development Release
« Reply #2 on: July 20, 2010, 09:26:50 am »
... and recommend using it for any new projects using wxWidgets....
No...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline lmame

  • Single posting newcomer
  • *
  • Posts: 3
Re: wxWidgets 2.9.1 Development Release
« Reply #3 on: July 21, 2010, 07:25:57 am »
It's a good thing because it seems building it under Windows is close to impossible for now (2.9.1 and svn).
Something wrong with scintilla linking and I can't figure it out for now :( I tried but as each build takes so much time... Out of my league...:
http://wxforum.shadonet.com/viewtopic.php?t=28386

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: wxWidgets 2.9.1 Development Release
« Reply #4 on: July 21, 2010, 09:01:25 am »
It's a good thing because it seems building it under Windows is close to impossible for now (2.9.1 and svn).
Something wrong with scintilla linking and I can't figure it out for now :( I tried but as each build takes so much time... Out of my league...:
http://wxforum.shadonet.com/viewtopic.php?t=28386

There are two ways. (Edit 1: I'm assuming release build is being built)
1) Change DEBUG_FLAG ?= 0 inside config.gcc file or issue DEBUG_FLAG=0 when enter make command in command prompt.
2) Manually edit setup.h file - uncomment line no 69 to 73 and then build.

Please note that you can build multi-lib build. Even after doing above Monolithic build throws one linker error which I could not figure out.

To read about the changes to build system read the following article.
Quote
http://wxwidgets.blogspot.com/2009/09/debug-build-changes-in-wx3.html
« Last Edit: July 21, 2010, 09:04:21 am by Biplab »
Be a part of the solution, not a part of the problem.

Offline lmame

  • Single posting newcomer
  • *
  • Posts: 3
Re: wxWidgets 2.9.1 Development Release
« Reply #5 on: July 21, 2010, 09:43:53 am »
Thanks for the reply and the link :)

I tried adding the debug flag in the make but I finished ending with the same linker errors:
Code: [Select]
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 DEBUG_FLAG=0  clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 DEBUG_FLAG=0

I'm trying now with the other solution(s).

And yeah you're right, the multi-lib is working ;)


Edit:
So I tried with both your solutions, both of them failed sadly, same error as before :(
« Last Edit: July 21, 2010, 06:20:32 pm by lmame »

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: wxWidgets 2.9.1 Development Release
« Reply #6 on: July 22, 2010, 11:28:51 am »
I tried adding the debug flag in the make but I finished ending with the same linker errors:
Code: [Select]
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 DEBUG_FLAG=0  clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 DEBUG_FLAG=0

....

Edit:
So I tried with both your solutions, both of them failed sadly, same error as before :(

I mentioned in my post before - Monolithic build is not working.
Be a part of the solution, not a part of the problem.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6510
    • My Best Post
Re: wxWidgets 2.9.1 Development Release
« Reply #7 on: July 23, 2010, 04:37:11 am »
I got Code::Blocks to compile/link/run against wx2.9.1.

Tim S.

Still crashes on shutdown. But the error might be mine; I built it used TDM 4.5 SJLJ but the codeblocks.RPT mentions Dwarf.
Going to try building using DW2. Only tested open and close; did not compile contrib plugins.

Built wx using wxPropertyGrid; but, without STC.
Note: You must use the wxWidgets version of wxPropertyGrid and remove most of wxPropertyGrid related stuff from CB project file.

Note: Remember to edit setup.h before building; wxUSE_STC needs set to 0.
Code: [Select]
mingw32-make.exe -f makefile.gcc USE_QA=1 USE_STC=0 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release


Hand edited source code patch needed for compile problem. wx2.9 wxString redesign issue.
Code: [Select]
Index: src/src/main.cpp
===================================================================
--- src/src/main.cpp (revision 6412)
+++ src/src/main.cpp (working copy)
@@ -1192,7 +1192,7 @@
         wxString key = wxString::Format(_T("/main_frame/layout/view%d/"), count);
         Manager::Get()->GetConfigManager(_T("app"))->Write(key + _T("name"), it->first);
         Manager::Get()->GetConfigManager(_T("app"))->Write(key + _T("data"), it->second);
-        if(m_LayoutMessagePane[it->first])
+        if(!m_LayoutMessagePane[it->first].IsEmpty())
         {
             Manager::Get()->GetConfigManager(_T("app"))->Write(key + _T("dataMessagePane"), m_LayoutMessagePane[it->first]);
         }


Code: [Select]
-------------------

Error occured on Thursday, July 22, 2010 at 22:35:18.

H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe caused a Breakpoint at location 7589194b in module D:\Windows\system32\KERNELBASE.dll.

Registers:
eax=00000006 ebx=029c8498 ecx=fa697179 edx=002b376c esi=02a58620 edi=029c8498
eip=7589194b esp=0022ea18 ebp=0022ea84 iopl=0         nv up ei pl nz ac po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000216

Call stack:
7589194B  D:\Windows\system32\KERNELBASE.dll:7589194B  DebugBreak
69F4480D  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F4480D  _ZN15wxAppTraitsBase16ShowAssertDialogERK8wxString
69F46E24  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F46E24  _Z10wxOnAssertPKciS0_S0_
69F47809  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F47809  _ZN16wxAppConsoleBase15OnAssertFailureEPKwiS1_S1_S1_
69F47389  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F47389  _Z10wxOnAssertPKciS0_S0_
69F44B27  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F44B27  _Z10wxOnAssertPKciS0_S0_PKw
6A37D25C  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A37D25C  _ZN12wxWindowBaseD1Ev
6A1B3E75  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A1B3E75  _ZN8wxWindowD2Ev
6A2A569E  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A2A569E  _ZN13wxControlBaseD2Ev
6A201557  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A201557  _ZN10wxListCtrlD1Ev
6A2015E6  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A2015E6  _ZN10wxListCtrlD0Ev
6A37A1B2  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A37A1B2  _ZN12wxWindowBase7DestroyEv
6A577E10  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A577E10  _ZN13wxAuiNotebook10DeletePageEj
6A578626  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A578626  _ZN13wxAuiNotebookD2Ev
0048E8E1  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:0048E8E1Dwarf Error: mangled line number section.  _ZN12cbToolPlugin9BuildMenuEP9wxMenuBar
004223F0  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:004223F0
0042248D  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:0042248D
6A37A1B2  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A37A1B2  _ZN12wxWindowBase7DestroyEv
004414B0  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:004414B0Dwarf Error: mangled line number section.
69F430BA  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F430BA  _ZNK16wxAppConsoleBase16CallEventHandlerEP12wxEvtHandlerR14wxEventFunctorR7wxEvent
6A0BFBC2  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFBC2  _ZN12wxEvtHandler23ProcessEventIfMatchesIdERK21wxEventTableEntryBasePS_R7wxEvent
6A0BFCF3  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFCF3  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
6A0C0124  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0C0124  _ZN12wxEvtHandler11TryHereOnlyER7wxEvent
6A0BFE01  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFE01  _ZN12wxEvtHandler10DoTryChainER7wxEvent
6A0C0212  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0C0212  _ZN12wxEvtHandler12ProcessEventER7wxEvent
6A0BFEC4  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFEC4  _ZN12wxEvtHandler18SafelyProcessEventER7wxEvent
6A37B2F2  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A37B2F2  _ZN12wxWindowBase5CloseEb
00440FAB  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:00440FABDwarf Error: mangled line number section.
69F430BA  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F430BA  _ZNK16wxAppConsoleBase16CallEventHandlerEP12wxEvtHandlerR14wxEventFunctorR7wxEvent
6A0BFBC2  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFBC2  _ZN12wxEvtHandler23ProcessEventIfMatchesIdERK21wxEventTableEntryBasePS_R7wxEvent
6A0BFCF3  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFCF3  _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler
6A0C0124  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0C0124  _ZN12wxEvtHandler11TryHereOnlyER7wxEvent
6A0BFE01  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFE01  _ZN12wxEvtHandler10DoTryChainER7wxEvent
6A0C0212  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0C0212  _ZN12wxEvtHandler12ProcessEventER7wxEvent
6A0BFEC4  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0BFEC4  _ZN12wxEvtHandler18SafelyProcessEventER7wxEvent
6A2E6FC1  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A2E6FC1  _ZN11wxFrameBase14ProcessCommandEP10wxMenuItem
6A1F2A7B  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A1F2A7B  _ZN7wxFrame13MSWWindowProcEjjl
6A1AEFAE  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A1AEFAE  _Z9wxWndProcP6HWND__jjl@16
76F386EF  D:\Windows\system32\USER32.dll:76F386EF  IsThreadDesktopComposited
76F38876  D:\Windows\system32\USER32.dll:76F38876  IsThreadDesktopComposited
76F389B5  D:\Windows\system32\USER32.dll:76F389B5  IsThreadDesktopComposited
76F38E9C  D:\Windows\system32\USER32.dll:76F38E9C  DispatchMessageW
6A0CDEFA  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0CDEFA  _ZN14wxGUIEventLoop14ProcessMessageEP6tagMSG
6A0CF373  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0CF373  _ZN14wxGUIEventLoop8DispatchEv
69F78D6E  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F78D6E  _ZN17wxEventLoopManual3RunEv
69F44F18  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69F44F18  _ZN16wxAppConsoleBase8MainLoopEv
0040640A  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:0040640ADwarf Error: mangled line number section.
69FC88A0  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:69FC88A0  _Z12wxInitializev
6A0CFFA9  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\wxmsw291u_gcc_custom.dll:6A0CFFA9  _Z7wxEntryP11HINSTANCE__S0_Pci
00401EAF  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:00401EAFDwarf Error: mangled line number section.
0047E1C6  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:0047E1C6
004010DB  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:004010DB
00401158  H:\SourceCode\Projects\IDEs\CodeBlocks\codeblocks-wx29-SJLJ\src\output\codeblocks.exe:00401158
77041194  D:\Windows\system32\kernel32.dll:77041194  BaseThreadInitThunk
774BB495  D:\Windows\SYSTEM32\ntdll.dll:774BB495  RtlInitializeExceptionChain
774BB468  D:\Windows\SYSTEM32\ntdll.dll:774BB468  RtlInitializeExceptionChain
« Last Edit: July 23, 2010, 05:27:40 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline lmame

  • Single posting newcomer
  • *
  • Posts: 3
Re: wxWidgets 2.9.1 Development Release
« Reply #8 on: July 23, 2010, 08:27:09 am »
Indeed it's building this way.

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: wxWidgets 2.9.1 Development Release
« Reply #9 on: July 23, 2010, 10:17:18 am »
If I remeber right, the crash on shutdown is not related to slj or dw2, but to closing/deleting eventhandlers (in this case the TextControlLoggers).
I did not find a clean way to avoid it until now, but also did not work on it since two months or so, because of a lack of time.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6510
    • My Best Post
Re: wxWidgets 2.9.1 Development Release
« Reply #10 on: July 23, 2010, 02:37:07 pm »
If I remeber right, the crash on shutdown is not related to slj or dw2, but to closing/deleting eventhandlers (in this case the TextControlLoggers).
I did not find a clean way to avoid it until now, but also did not work on it since two months or so, because of a lack of time.

Yes, I agree event handlers were the cause of the 2.9.0 or early 2.9.1 trunk shutdown issue; and TextControlLoggers sound like the class that was having the issues.
All I remember was it was a class with Loggers and/or Logger in the name was involved.

Tim S.
« Last Edit: July 23, 2010, 02:56:30 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org