now that I've gotten wxPython installed on my linux box at home, I need to get it working on my Mac here at work. Unfortunately, I can't get it to compile:
gcc -Wno-long-double -no-cpp-precomp -fno-common -dynamic -DNDEBUG -g - -O3 -Wall -Wstrict-prototypes -DSWIG_GLOBAL -DHAVE_CONFIG_H - -DWXP_USE_THREAD=1 -UNDEBUG -Isrc - -I/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3 - -c src/mac/controls.cpp -o build/temp.darwin-6.6-Power_Macintosh-2.3/src/mac/controls.o - -I/usr/local/lib/wx/include/macd-2.4 -D__WXDEBUG__ -D__WXMAC__ - -DWXMAKINGDLL -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES
src/mac/controls.cpp: In function `void wxComboBox_Append(wxComboBox*, const
wxString&, PyObject*)':
src/mac/controls.cpp:3587: no matching function for call to `wxComboBox::Append
(const wxString&, wxPyClientData*&)'
/usr/local/include/wx/mac/combobox.h:68: candidates are: virtual void
wxComboBox::Append(const wxString&)
error: command 'gcc' failed with exit status 1
now that I've gotten wxPython installed on my linux box at home, I need to get it working on my Mac here at work. Unfortunately, I can't get it to compile:
Which wxMac did you build and install? On the Mac you definitly want to build wxMac from the wxPythonSrc tarball because I've included a couple patches that are not in the official releases for 2.4.x because of binary compatibility issues.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I've solved the problem by installing the wxPython-dev binary package, and
just copying the headers from CVS... I don't need to do a heck of a lot with
the wxPython source, just pass in some parent frames from time to time. It
appeared to be working, but i haven't tried passing wxWindow pointers yet...
I had to replace the wx-macd libs with my own versions because I need some
adjustments I've made to the wxWindows source (I've prebound them and added
some shared-library fixes, as well as adding in the OGL code to avoid having
to deal with prebinding yet another library). Will I run into problems with
this type of setup? I really would like to use the CVS tree, because there
are some bug fixes since 2.4.1 that I'm fond of :->
Thanks,
Nick
···
On Monday 21 July 2003 06:15 pm, Robin Dunn wrote:
Nicholas Burlett wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> now that I've gotten wxPython installed on my linux box at home, I need
> to get it working on my Mac here at work. Unfortunately, I can't get it
> to compile:
Which wxMac did you build and install? On the Mac you definitly want to
build wxMac from the wxPythonSrc tarball because I've included a couple
patches that are not in the official releases for 2.4.x because of
binary compatibility issues.
I've solved the problem by installing the wxPython-dev binary package, and just copying the headers from CVS... I don't need to do a heck of a lot with the wxPython source, just pass in some parent frames from time to time. It appeared to be working, but i haven't tried passing wxWindow pointers yet...
I had to replace the wx-macd libs with my own versions because I need some adjustments I've made to the wxWindows source (I've prebound them and added some shared-library fixes,
If you could give details on these I would appreciate it.
as well as adding in the OGL code to avoid having to deal with prebinding yet another library). Will I run into problems with this type of setup?
Probably not.
I really would like to use the CVS tree, because there are some bug fixes since 2.4.1 that I'm fond of :->
The patches that I applied are in the wxPythonSrc tarball in the patches dir, and would probably still apply cleanly to a 2.4 CVS tree.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
In the 2_4_BRANCH, the dynamic lib (dynlib.cpp) loader is broken on MacOS X. It is capable of loading symbols from files, but if you try to load multiple files with the same symbol (as you do in a plugin architecture), then it always returns the symbol loaded from the first loaded object. In CVS HEAD, it appears to be fixed. I've fixed it in my copy essentially the same way it is fixed there.
As far as prebinding, I adjusted the build procedure so that the final link looked like this:
../distrib/mac/shared-ld-sh -prebind -seg1addr 0xe2000000 - -flat_namespace -o lib/libwx_macd-2.4.0.0.0.dylib - -compatibility_version 2.4 -current_version 2.4.1 -install_name /usr/local/lib/libwx_macd-2.4.0.dylib DirectoryCopy.o .....
The seg1addr is set to that so that it doesn't overlap with either the application I'm writing, or the Framework that the application uses.
I hope this helps.
- --
Nicholas Burlett
nrb23@cornell.edu
···
On Tuesday, July 22, 2003, at 01:43 PM, Robin Dunn wrote:
nrb23@cornell.edu wrote:
I've solved the problem by installing the wxPython-dev binary package, and just copying the headers from CVS... I don't need to do a heck of a lot with the wxPython source, just pass in some parent frames from time to time. It appeared to be working, but i haven't tried passing wxWindow pointers yet...
I had to replace the wx-macd libs with my own versions because I need some adjustments I've made to the wxWindows source (I've prebound them and added some shared-library fixes,
If you could give details on these I would appreciate it.