From: William S F. <ws...@fu...> - 2016-01-28 19:16:20
|
Hi Phineas Great to hear you have some time and resources on hand to help. Time to develop and improve SWIG will be much appreciated as we are an all volunteer project with stretched resources. I suggest you find something that looks interesting to you from one of the bugs in the github bug tracker. Check before heading off doing too much though as some are not particular important nor correct. Maybe others have some ideas of what you could do? As you have both windows and Linux boxes, I would like to suggest providing the CMake builds. There is a recent discussion on this earlier this month which you can see at http://thread.gmane.org/gmane.comp.programming.swig.devel/23775/focus=23780 . You could provide a patch to get the CMakeLists.txt file to work with the current build. If you follow the mails, you'll see I'd like to have a CMakeLists.txt file that works with the automake buildsto build swig.exe. In particular it should share the list of source files for compiling swig.exe. Additionally, I'd like it use a common Source/Include/ swigconfig.h.in. If you fancy some JNI coding, new versions of Java 1.8 are highlighting problems with the use of -Xcheck:jni which need resolving. I have replicated them on Linux (latest jdk 1.8) but can also be seen on Appveyor which is the Windows Continuous Integration testing platform we use - https://ci.appveyor.com/project/swig/swig. With regards to spaces in paths, my view is that this is really a user's problem in a build system and not really anything to do with SWIG. If someone wants to put spaces in paths to make life really hard for any command line tool, like SWIG and any other type of compiler, then they are welcome to waste time doing it when there are more interesting things to do! The only time we really need this is for our own test-suite when system headers are installed in locations that have spaces. This is usually just a Windows problem, eg the JDK is often installed in something with "Program Files" in the path. The autotools build system was fixed for Java and C# when I set up these languages on Appveyor. I think all the other languages install in a sensible location without spaces, but we don't actually test them on Windows/Appveyor. William On 27 January 2016 at 15:18, Phineas Campbell <ph...@ph...> wrote: > I would like to get involved with the SWIG project. > > I have an XP machine with Visual Studio 2010, CPython, Python 3.4.1. > > I have a dual boot Windows 7 Ubuntu 14.04 machine with Python 3.4 dev and > 2.7 dev, gcc 4.8.4. I have with some difficulty built SWIG 3.0.8. I have > no emotional attachment to this machine and will rebuild as and when > necessary. > > I have no specific requests however I think I came across a situation in > which SWIG will takes spaces in path and others where it will not. I have > tried to replicate the situation but all paths passed to swig on Windows > with spaces fail. This is not important to me, it makes running swig with > CPython in debug in Visual Studio complicated. > > I am not a C++ guru but if it is in The C++ Programming Language I > understand, or can pick it up in an hour or two. I happy to work in either > Windows or Linux but prefer make files to IDEs > > So I have a lot of time, a bit of money to make a donation, a bit of skill > and prepared to do anything no matter how menial. > > > > Many thanks > > Phineas Campbell > > https://github.com/PhineasCampbell > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > Swig-devel mailing list > Swi...@li... > https://lists.sourceforge.net/lists/listinfo/swig-devel > > |