Jonne Nauha <[email protected]> kirjoitti Jun 29, 2012 kello 4:37 PM: > I think those issues were only in the initial windows full build script as it > had qt 4.8. The py deps should build ok now that we reverted to 4.7.4. Just > Ah - I still thought that would need to rebuild the deps against new qt etc. > The real problem is that the py module has no active maintainer. Toni (the > inactive maintainer :) said he will fix the deps build 2-3 months ago, I > guess he is busy. > I did get to work on it on a couple of days recently - enough to get a Windows Tundra dev running. I don't usually dev Tundra on Win so the old setups were outdated, also wanted to test the new scripts. Had some prob then with fullbuild which have still been unable to solve, doesn't compile iirc.
I did get a working build with your new prebuilt deps using script. But releases are made with the full build one, so for that should get it working there I suppose - right? > The deps and module is enabled and working in the linux build script, its > incomplete only in the windows script. > Yep, and we've been using Py for server side things mostly with Tundra recently and haven't needed Win there so hasn't been a prob in WebNaali tests etc. I heard that mopo/chiru at the uni are using py for some app things too, though - don't know how much for client/server sides (I heard a XMPP chat gui was written in py there). I'm not sure if we want to include py in standard Tundra client downloads as those seem to be big (on win) even without it. On Linux (usually) and Mac (always) perhaps less an issue as the OS already comes with it (including the standard lib which we've bundling for Win) -Toni -- http://groups.google.com/group/realxtend http://www.realxtend.org
