I'm trying to build the rv6python extension for Python 2.0 using the TIBCO 6.5 release on a Solaris 2.6 platform. In the setup script in the run method for the my_build_ext class, there's a call to self.run_peer('build_swig'). However, the setup script fails as there is no run_peer method in the my_build_ext class. What should be going on here? Should an instance of my_build_swig be available to the instance of my_build_ext?
Also, it might be a good idea to put the configurable items like default_rv_home and sysconfig.CC and such into a setup.cfg file. This would make it more apparent to builders what the configurable items are.
Lastly, since the use of distutils is still fairly new, it still is probably a good idea to include a README.txt file with the distribution outlining the steps required to build the distribution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found a comment in a Python CVS log that indicated that "run_peer" has been renamed to "run_command". Making this change allowed everything to proceed.
I made that changed and got as far as finding out that something called "swig" was needed. I guess this is the thing http://www.swig.org/. Now I must run the gauntlet of our firewall once more.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I thought I needed swig because I had deleted rv6.c (probably by running "python setup.py clean"). If you ensure you have the rv6.c that is distributed then it won't be necessary to run swig.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to build the rv6python extension for Python 2.0 using the TIBCO 6.5 release on a Solaris 2.6 platform. In the setup script in the run method for the my_build_ext class, there's a call to self.run_peer('build_swig'). However, the setup script fails as there is no run_peer method in the my_build_ext class. What should be going on here? Should an instance of my_build_swig be available to the instance of my_build_ext?
Also, it might be a good idea to put the configurable items like default_rv_home and sysconfig.CC and such into a setup.cfg file. This would make it more apparent to builders what the configurable items are.
Lastly, since the use of distutils is still fairly new, it still is probably a good idea to include a README.txt file with the distribution outlining the steps required to build the distribution.
I found a comment in a Python CVS log that indicated that "run_peer" has been renamed to "run_command". Making this change allowed everything to proceed.
I made that changed and got as far as finding out that something called "swig" was needed. I guess this is the thing http://www.swig.org/. Now I must run the gauntlet of our firewall once more.
I thought I needed swig because I had deleted rv6.c (probably by running "python setup.py clean"). If you ensure you have the rv6.c that is distributed then it won't be necessary to run swig.