Vaclav and I noticed that some of the components that make up the -devel package on Windows and Linux do not get installed when doing a source build. (i.e. make install && python setup.py install) Particularly, what's missing are the wxPython includes and the i_files folder. It would simplify things if these files for *nix at least if these were always installed during a wxPython source build.
The question then becomes how to do this. As far as I can see, there're two basic ways to resolve this - modifying wxWidgets' make install process to install those files (and probably adding some sort of configure flag to enable it, like --enable-wxpython) or have "python setup.py install" install the files. The more I think about this, the more I'm not sure what the best approach should be. Going the python route, there will be problems if the person installing the Python extensions doesn't have write access to the folder where the wx libs are installed. However, going the wxWidgets route it seems a shame (and counter-intuitive) that a flag like --enable-wxpython wouldn't actually do anything to build wxPython, and would just dump some files when make install is run. If it did what it says, however, it would probably become a lot of work to implement. ;-/ I guess we could actually have something set in the makefile like:
make install WXPYTHON_FILES=1
which probably wouldn't be too intrusive, but is a bit more clunky and hard to remember. Anyways, what do you guys think?
Vaclav and I noticed that some of the components that make up the -devel package on Windows and Linux do not get installed when doing a source build. (i.e. make install && python setup.py install) Particularly, what's missing are the wxPython includes and the i_files folder. It would simplify things if these files for *nix at least if these were always installed during a wxPython source build.
The question then becomes how to do this. As far as I can see, there're two basic ways to resolve this - modifying wxWidgets' make install process to install those files (and probably adding some sort of configure flag to enable it, like --enable-wxpython) or have "python setup.py install" install the files. The more I think about this, the more I'm not sure what the best approach should be. Going the python route, there will be problems if the person installing the Python extensions doesn't have write access to the folder where the wx libs are installed. However, going the wxWidgets route it seems a shame (and counter-intuitive) that a flag like --enable-wxpython wouldn't actually do anything to build wxPython, and would just dump some files when make install is run. If it did what it says, however, it would probably become a lot of work to implement. ;-/ I guess we could actually have something set in the makefile like:
make install WXPYTHON_FILES=1
which probably wouldn't be too intrusive, but is a bit more clunky and hard to remember. Anyways, what do you guys think?
setup.py is already supposed to be doing it. Take a look at how HEADERS is set and also the wx_install_headers custom class. It should be installing the headers to wherever the wx headers are located, (and just did in my quick test.)
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!