Preparing CORE...
Preparing GLCANVAS...
Preparing OGL...
Preparing STC...
Preparing XRC...
Preparing GIZMOS...
running build
running build_py
copying wxPython/__version__.py -> build/lib.linux-i686-2.3/wxPython
running build_ext
building 'wxc' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -g -fPIC -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -UNDEBUG -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Isrc -I/usr/local/lib/wx/include/gtkd-2.5 -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -I/usr/include/python2.3 -c src/gtk/misc2.cpp -o build/temp.linux-i686-2.3/src/gtk/misc2.o -O3
src/gtk/misc2.cpp: In function `bool wxThread_IsMain()':
src/gtk/misc2.cpp:120: `wxThread' undeclared (first use this function)
src/gtk/misc2.cpp:120: (Each undeclared identifier is reported only once for each function it appears in.)
src/gtk/misc2.cpp:120: parse error before `::' token
error: command 'gcc' failed with exit status 1
Seems something is broken
Is this fully CVS HEAD or is it HEAD + the wxPy_newswig wxPython branch? (I've been ignoring the former for a coupel weeks now while working on the latter.)
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
> Would it be possible for it to also check the "d" - debug version?
It will if you add the --debug command-line flag to setup.py
Great, I'll try that.
> Seems something is broken
Is this fully CVS HEAD or is it HEAD + the wxPy_newswig wxPython branch?
(I've been ignoring the former for a coupel weeks now while working on
the latter.)
Ah. I track the wxWindows CVS HEAD. I'll have to examine the other fork in the
road
That will be useful because in Mahogany at present, I'm trying to get it
working with the new SWIG so I'll see if you have fixed what I am puzzling
over. Typemaps are not my idea of fun
MarkL
···
On Mon, 03 Nov 2003 16:31:22 -0800 Robin Dunn <robin@alldunn.com> wrote:
OK. At present, as I said, I track the wxWindows anonCVS HEAD and so get the
wxPython stuff that you are currently not working actively on.
I just go to ~/projects/wxWindows and do CVS UPDATE and it all works.
How would I go about making it track what you are working on?
Do I have to make different cvs image just for the newswig branch and then
when you merged it back into the CVS HEAD would I have to do something to make
it track the new situation then?
TIA
MarkL
···
On Fri, 7 Nov 2003 10:55:20 +1000 (EST) Mark Livingstone <mlivingstone@iprimus.com.au> wrote:
> Is this fully CVS HEAD or is it HEAD + the wxPy_newswig wxPython branch?
> (I've been ignoring the former for a coupel weeks now while working on
> the latter.)
Ah. I track the wxWindows CVS HEAD. I'll have to examine the other fork in the
road
I just downloaded the 2.4.2.4 rpm's and while having a 'senior moment' tried
to build the 2.4.2.4 wxPython against my current 2.5.1 wxWindows. It stopped
at the same place giving exactly the same message as below about
wxThread_IsMain(). Does this mean there is a real problem at that point in wx
code or could I have mucked it up some other way
I'm just thinking, I may have told wxWindows to build without threads since
they are not used for Mahogany. Could that be the cause?
···
On Fri, 31 Oct 2003 19:12:21 +1000 mlivingstone <mlivingstone@iprimus.com.au> wrote:
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fomit-frame-pointer
-pipe -march=i586 -mcpu=pentiumpro -g -fPIC -DSWIG_GLOBAL
-DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -UNDEBUG -D__WXDEBUG__ -D__WXGTK__
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Isrc
-I/usr/local/lib/wx/include/gtkd-2.5 -I/usr/include/gtk-1.2
-I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include
-I/usr/include/python2.3 -c src/gtk/misc2.cpp -o
build/temp.linux-i686-2.3/src/gtk/misc2.o -O3
src/gtk/misc2.cpp: In function `bool wxThread_IsMain()':
src/gtk/misc2.cpp:120: `wxThread' undeclared (first use this function)
src/gtk/misc2.cpp:120: (Each undeclared identifier is reported only
once for each function it appears in.)
src/gtk/misc2.cpp:120: parse error before `::' token
error: command 'gcc' failed with exit status 1
How would I go about making it track what you are working on?
Go into the wxPython dir and do "cvs update -r wxPy_newswig"
Do I have to make different cvs image just for the newswig branch and then
when you merged it back into the CVS HEAD would I have to do something to make
it track the new situation then?
No just do "cvs update -A" to remove the sticky tag.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I just downloaded the 2.4.2.4 rpm's and while having a 'senior moment' tried
to build the 2.4.2.4 wxPython against my current 2.5.1 wxWindows. It stopped
at the same place giving exactly the same message as below about
wxThread_IsMain(). Does this mean there is a real problem at that point in wx
code or could I have mucked it up some other way
I'm just thinking, I may have told wxWindows to build without threads since
they are not used for Mahogany. Could that be the cause?
Yep.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
On Fri, 07 Nov 2003 19:54:51 -0800 Robin Dunn <robin@alldunn.com> wrote:
> Mark Livingstone wrote:
> > How would I go about making it track what you are working on? > > > > Go into the wxPython dir and do "cvs update -r wxPy_newswig"
OK. Did that and saw how much you actually have been working lately!
Hmm, I wonder why I am not getting that, probably because I usually use the --inplace flag while working on things day to day. Anyway, it is probably just a tweak needed to setup.py. I'll look into it in a few minutes and check in a fix.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I have now managed to build --debug and install the wxPython CORE and GLCANVAS.
When I try to build OGL / STC / XRC / GIZMOS I get a zillion *_wrap.cpp errors
which I presume means you are working on those parts?
contrib/ogl/ogl_wrap.cpp:618: syntax error before `sizeof'
contrib/ogl/ogl_wrap.cpp:619: cannot declare member function `wxPyPolygonShape::wxCreateObject' within `wxPyShapeCanvas'
contrib/ogl/ogl_wrap.cpp:619: syntax error before `{' token
contrib/ogl/ogl_wrap.cpp:619: parse error before `::' token
contrib/ogl/ogl_wrap.cpp:619: cannot declare member function `wxPyPolygonShape::ms_classInfo' within `wxPyShapeCanvas'
contrib/ogl/ogl_wrap.cpp:619: syntax error before `sizeof'
contrib/ogl/ogl_wrap.cpp:620: cannot declare member function `wxPyTextShape::wxCreateObject' within `wxPyShapeCanvas'
contrib/ogl/ogl_wrap.cpp:620: syntax error before `{' token
contrib/ogl/ogl_wrap.cpp:620: parse error before `::' token
contrib/ogl/ogl_wrap.cpp:620: cannot declare member function `wxPyTextShape::ms_classInfo' within `wxPyShapeCanvas'
contrib/ogl/ogl_wrap.cpp:620: syntax error before `sizeof'
contrib/ogl/ogl_wrap.cpp:632: cannot declare static function inside another function
contrib/ogl/ogl_wrap.cpp: In function `PyObject* _wrap_new_ShapeRegion(PyObject*, PyObject*, PyObject*)':
contrib/ogl/ogl_wrap.cpp:634: `wxShapeRegion' undeclared (first use this function)
contrib/ogl/ogl_wrap.cpp:634: `result' undeclared (first use this function)
contrib/ogl/ogl_wrap.cpp:642: parse error before `)' token
contrib/ogl/ogl_wrap.cpp:639: confused by earlier errors, bailing out
{standard input}: Assembler messages:
{standard input}:167: Error: symbol `wxPyMake_wxShapeEvtHandler' is already defined
I have successfully made the relevant bits in wxWindows.
If you do want to know the errors you will have to tell me how to save the
errors to a file as they scroll offscreen at a great rate of knots!
I tried to get it to use SWIG but it complained because you look in
/opt/bin/swig/bin and mine is in /usr/bin/swig. I didn't look very hard to see
where you have hardcoded it.
When I tried DLLWIDGET it said:
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -g -fPIC -g -DSWIG_GLOBAL -DHAVE_CONFIG_H -DWXP_USE_THREAD=1 -UNDEBUG -D__WXDEBUG__ -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -Iinclude -Isrc -I/usr/local/lib/wx/include/gtkd-2.5 -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -I/usr/include/python2.3 -c contrib/dllwidget/dllwidget.cpp -o build/temp.linux-i686-2.3/contrib/dllwidget/dllwidget.o -g -O0
contrib/dllwidget/dllwidget.cpp: In static member function `static wxString wxDllWidget::GetDllExt()':
contrib/dllwidget/dllwidget.cpp:67: `wxDllLoader' undeclared (first use this function)
contrib/dllwidget/dllwidget.cpp:67: (Each undeclared identifier is reported only once for each function it appears in.)
contrib/dllwidget/dllwidget.cpp:67: parse error before `::' token
error: command 'gcc' failed with exit status 1
I tried install --debug but I just get a usage summary. When I ty install on
it's own, it complains:
[root@sovereign wxPython]# python setup.py install WX_CONFIG not specified and
wxgtk-2.5-config not found on $PATH defaulting to "wx-config"
But if it knew about --debug it would know to look for wxgtkd*
HTH / TIA
MarkL
···
On Mon, 10 Nov 2003 13:34:16 -0800 Robin Dunn <robin@alldunn.com> wrote:
> error: package directory 'wxPython/lib/PyCrust' does not exist
> [root@sovereign wxPython]#
>
> Now what?
Hmm, I wonder why I am not getting that, probably because I usually use
the --inplace flag while working on things day to day. Anyway, it is
probably just a tweak needed to setup.py. I'll look into it in a few
minutes and check in a fix.
> > error: package directory 'wxPython/lib/PyCrust' does not exist
> > [root@sovereign wxPython]#
> > > > Now what? > > Hmm, I wonder why I am not getting that, probably because I usually use > the --inplace flag while working on things day to day. Anyway, it is > probably just a tweak needed to setup.py. I'll look into it in a few > minutes and check in a fix.
OK. That fix worked well.
I have now managed to build --debug and install the wxPython CORE and GLCANVAS.
When I try to build OGL / STC / XRC / GIZMOS I get a zillion *_wrap.cpp errors
which I presume means you are working on those parts?
They work here.
[...]
I have successfully made the relevant bits in wxWindows.
If you do want to know the errors you will have to tell me how to save the
errors to a file as they scroll offscreen at a great rate of knots!
Just redirect the output of the command to a file like usual.
I tried to get it to use SWIG but it complained because you look in
/opt/bin/swig/bin and mine is in /usr/bin/swig. I didn't look very hard to see
where you have hardcoded it.
It hasn't been hard coded for about a week, but you *will* need to use the CVS version of SWIG, or get 1.3.20 when it is released. (I guess I should do a version check...) You can use a SWIG=pathname on the setup.py command line to specifiy an alternate swig if needed.
When I tried DLLWIDGET it said:
I havn't updated DLLWIDGET in a long time, that is why it is disabled by default in setup.py
I tried install --debug but I just get a usage summary. When I ty install on
it's own, it complains:
[root@sovereign wxPython]# python setup.py install WX_CONFIG not specified and
wxgtk-2.5-config not found on $PATH defaulting to "wx-config"
But if it knew about --debug it would know to look for wxgtkd*
You can specify a WX_CONFIG=pathname on the command line to use a specific instance of the config script if needed.
···
On Mon, 10 Nov 2003 13:34:16 -0800 Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
