On 3 Aug, 20:07, William Stein <wst...@gmail.com> wrote: > On Mon, Aug 3, 2009 at 12:02 PM, Ondrej Certik<ond...@certik.cz> wrote: > > > On Wed, May 13, 2009 at 10:46 AM, Brian Granger<ellisonbg....@gmail.com> > > wrote: > > >> I just pinged the pythonmac-sig group about why and when a framework > >> build is actually needed. A while back I created an spkg for qt/pyqt > >> and I remember that I needed to do a framework build to get it to > >> work. My recollection is that if you want Python to be able to do > >> anything with the native Mac GUI, it needs to be a framework build. > >> If this is indeed the case, I think it would be a great idea to have > >> the Sage python be a framework build and I have an older spkg around > >> somewhere that does this without any bugs (that I know of ;-)). I > >> know that in SPD, we would like to be able to have an spkgs for > >> matplotlib that includes real GUI support. Plus I know that some > >> folks are obviously linterested in VTK, Mayavi stuff as well. > > >> I will dig up my framework python spkg and get back after I hear from > >> the pythonmac-sig folks. > > > Could you please share it? I have created sip (sip is something like > > swig, needed to built pyqt) and pyqt packages here: > > >http://femhub.googlecode.com/files/sip.spkg > >http://femhub.googlecode.com/files/pyqt.p1.spkg > > > the sip is 0.5MB, pyqt is 1MB, sip builds instantly, pyqt in about 10 > > min on my laptop and 7 min on my workstation (not in parallel). > > > So it nicely works on linux, however on mac, the sip package refuses > > to build, because python is not built with framework support. > > > I will use pyqt using traits-qt backend for my gui applications. > > > VTK also doesn't build without the framework support, but we'll look > > at it at scipy09 with Prabhu, so maybe we'll fix it. however, from > > what I understood above, there is no way to fix pyqt to work with Sage > > on Mac, unless we use framework. > > > Am I missing something? If that is the case, then it's an absolute > > showstopper for me, if I can't use Sage as a framework for our gui > > apps. I don't have time thought to invest it into porting things to > > mac, so for the time being I chose the strategy to disable packages > > that just don't build on Mac in our distribution (femhub.org) and > > that's it. > > > Also, what is the state of the windows port of Sage --- will it be > > possible to just maintain one spkg and it would build on windows, or > > will it be necessary to maintain one spkg for linux/mac and another > > one for windows? > > At present the Windows port spkg's are completely different than on Linux/mac. > Obviously that's not what we want in the long run. However, things > are *very* different in Windows land than UNIX land, and something > that works under UNIX isn't going to "just work" under native Windows. > > -- William
The packages work in a different way but in theory if you provide an spkg-windows.bat script in the root of your spkg and following the simple set of rules set out in the Windows' port "spkg\examples\" folder (renamed in next release to "local\build_lib\templates\") then you're mostly there. However, you will still need to make sure your package builds with Visual Studio and/or nmake. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
