I am working on building wxpython on MacOS X and have a few questions. I
have wxMac 2.3.1 built and working - there are a few issues but it is
basically there. I am now working on wxPython 2.3.1 (both of these are
from the 2.3.1 cvs).
1) In previous messages about porting to motif and mac you mentioned that
there were some changes that needed to be made to app.cpp. From looking at
the msw app.cpp it appears that this is breaking up wxEntry into three
steps (wxEntryStart, wxEntryInitGui, wxEntryCleanup) - is this all that is
needed?
2) Drag and drop is not supported in the version of wxMac so I know that I
need to disable it in the .i files, but it appears that drag and drog
functionality is not localized and I am afraid that simply commenting out
all of the relevant dnd methods will not be sufficient. Any suggestions
about this?
3) Is it still necessary to use the specific version of swig listed in the
readme under SWIG? Also, any suggestions on generating the .i files of
linux and then doing the compilation under MacOS X (this is to avoid
porting swig).
Thanks,
Karl
···
---------------------
Karl W. MacMillan
Computer Music Department
Peabody Institute of the Johns Hopkins University
karlmac@peabody.jhu.edu
mambo.peabody.jhu.edu/~karlmac
1) In previous messages about porting to motif and mac you mentioned that
there were some changes that needed to be made to app.cpp. From looking at
the msw app.cpp it appears that this is breaking up wxEntry into three
steps (wxEntryStart, wxEntryInitGui, wxEntryCleanup) - is this all that is
needed?
Probably.
2) Drag and drop is not supported in the version of wxMac so I know that I
need to disable it in the .i files, but it appears that drag and drog
functionality is not localized and I am afraid that simply commenting out
all of the relevant dnd methods will not be sufficient. Any suggestions
about this?
What I usually do is add stuff on wxMSW and then if/when part of it doesn't
compile on wxGTK because of missing classes or methods I just #ifdef them
out in the .i files. (Sometimes I make empty stubs, but most of the time
it's just #ifdef's.)
3) Is it still necessary to use the specific version of swig listed in the
readme under SWIG?
Yes.
Also, any suggestions on generating the .i files of
linux and then doing the compilation under MacOS X (this is to avoid
porting swig).
I expect that SWIG should build on OS X. I will probably be trying it later
today once the dev tools CD gets here... (I just got a loaner box from
Apple but they forgot the software.)
···
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
I expect that SWIG should build on OS X. I will probably be trying it later
today once the dev tools CD gets here... (I just got a loaner box from
Apple but they forgot the software.)
Well, the latest stable swig didn't compile but it is probably just minor
issues. The developer tools are avaible from the apple site - just log
into the adc and go to the downloads. Of course it is kind of big which is
perhaps why you are waiting for the CD. Since you are working on this I
will just wait. If you would like any help please let me know.
Thanks,
Karl
···
On Tue, 28 Aug 2001, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
---------------------
Karl W. MacMillan
Computer Music Department
Peabody Institute of the Johns Hopkins University
karlmac@peabody.jhu.edu
mambo.peabody.jhu.edu/~karlmac