26-okt-2006, at 20:06, Robin Dunn wrote:
Sander Niemeijer wrote:
I just made a temporary symbolic link from this gtk1
subdirectory (named include/wx/gtk) and tried to see how much
further I could get.
The next problem occurred when trying to compile _core_wrap.o:
cc1plus: warning: command line option "-Wstrict-prototypes" is
valid for C/C but not for C++
src/gtk/_core_wrap.cpp: In function 'P*
_wrap_GetAccelFromString(P*, P*, P*)':
src/gtk/_core_wrap.cpp:30339: warning: 'wxGetAccelFromString' is
deprecated (declared at /
wx-2.7/wx/utils.h:571)
src/gtk/_core_wrap.cpp:30339: warning: 'wxGetAccelFromString' is
deprecated (declared at /
wx-2.7/wx/utils.h:571)
src/gtk/_core_wrap.cpp: In function 'P*
_wrap_Window_SetDoubleBuffered(P*, P*, P*)':
src/gtk/_core_wrap.cpp:34445: error: 'class wxWindow' has no
member named 'SetDoubleBuffered'
This one can be fixed with a patch to include/wx/gtk1/window.h.
Add something like this to the wxWindow declaration:
void SetDoubleBuffered(bool ) {}
>Patch submitted.
>
I didn't see this patch.
Sorry. I forget to submit it. It should be there now.
>Now the next thing that I found was an error when compiling src/
>gtk/_controls_wrap.cpp (the _controls_ extension):
>
>cc1plus: warning: command line option "-Wstrict-prototypes" is
>valid for C/C but not for C++
>src/gtk/_controls_wrap.cpp: In function 'P*
>_wrap_TextCtrl_SetModified(P*, P*, P*)':
>error: no matching function for
>call to 'wxTextCtrl::SetModified(bool&)'
>/
>140: note: candidates are: void wxTextCtrl::SetModified()
>
>I don't really understand this error. wxTextCtrl for gtk1 has its
>own SetModified() without parameters (and this won't work here),
>however wxTextCtrlBase (the parent class) does have a SetModified
>() that takes a bool as parameter. Any ideas how to fix this?
>
It probably needs to be tested, but it looks like you can just
remove the SetModified in gtk1/textctrl.h, I think the one in the
base class should work ok. If not then I would just change the
derived class version to take the bool parameter and set m_modified
to the value of the parameter.
I also just submitted a patch for this.
Then on with the build and I get this:
cc1plus: warning: command line option "-Wstrict-prototypes" is valid
for C/C but not for C++
In function 'P*
_wrap_new_GLContext(P*, P*, P*)':
error: no matching
function for call to 'wxGLContext::wxGLContext(wxGLCanvas*&, const
wxGLContext*)'
/
note: candidates are: wxGLContext::wxGLContext(bool, wxWindow*, const
wxPalette&, const wxGLContext*)
/
note: wxGLContext::wxGLContext(bool, wxWindow*, const
wxPalette&)
/
note: wxGLContext::wxGLContext(const wxGLContext&)
In function 'P*
_wrap_GLContext_SetCurrent(P*, P*, P*)':
error: no matching
function for call to 'wxGLContext::SetCurrent(const wxGLCanvas&)'
/
note: candidates are: void wxGLContext::SetCurrent()
In function 'P*
(P*, int, P**)':
error: no matching
function for call to 'wxGLCanvas::SetCurrent(const wxGLContext&)'
/
143: note: candidates are: void wxGLCanvas::SetCurrent()
This is starting to get very tiresome. I don't mind helping fixing an
issue here and there, but I just don't have time to take on full
maintenance for the GTK1 backend. Especially if every new change to
the GTK2 backend might break the GTK1 backend again.
Fortunately, yesterday I tried to build our application with wxPython
2.7 and the latest version of VTK using GTK2 and the z-ordering
issues we saw with the wxvtk binding and earlier versions of wxPython
are gone now. So I think I am now going to focus my efforts on
wxPython with GTK2.
P.S. If the situation with GTK1 does not improve, then might I
suggest putting a big warning sign somewhere for people who want to
try to use this backend. It will also reflect rather badly on the
image of the whole toolbox if people are confronted with all these
build errors.
Best regards,
Sander
To unsubscribe, e-mail: wxPython-users-unsubscribe (AT) lists (DOT) wxwidgets.org
For additional commands, e-mail: wxPython-users-help (AT) lists (DOT) wxwidgets.org