Hi,
Thanks for your email!
I'm pretty sure that it's using the correct wxGTK libs since I'm the
first one who installed it successfully on the machine.
It seems like there is some mismatching options between configure and
setup.h. Like you said, this might be the problem. There is a
setup.h.in file which seems to be the basis for setup.h. I know that
setup.h is generated when I do configure, but I'm not sure how
setup.h.in impacts the generated setup.h. As far as I can tell,
setup.h.in seems to overwrite the options by configure. Am I correct?
Yes. On unix platforms setup.h is almost totally generated by configure, setup.h.in is just a template.
Due to a lot of conditional compilation, without setting these options
correctly, I get many link errors.
I'm still not clear why when I ran "python demo.py", I got this error
message "wxPython used 2.6 (no debug,ANSI,wx containers,compatible with
2.4)" since I enabled debug for both wxGTK and wxPython as in BUILD.txt.I'm currently trying to compile & link without debug to see if this
makes any difference. I'm having trouble doing this since there is some
conditional compilation due to no __WXDEBUG__, I'm having link error
with "0711-317 ERROR: Undefined symbol: .wxAssert(int,const
char*,int,const char*,const char*) running build_ext". Since no debug,
it sets NDEBUG which sets no __WXDEBUG__ and wxAssert is not compiled
because of that.
Oh, I forgot about that. There should be some code in setup.py that adds a -UNDEBUG flag to the compilation command to undefine NDEBUG. This is added because Python automatically adds the -DNDEBUG flag instead of leaving it to be an option controlled by the builder as is the usual convention. If your compiler can't handle having both the define and the undefine on the command-line then that may be the source of this problem.
ยทยทยท
Min.Kim@aps.com wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!