On Tue, Jun 30, 2009 at 10:43 AM, Brian Granger<ellisonbg....@gmail.com> wrote: > >> One important >> thing to note is where the Framework goes. It will be installed in >> $SAGE_LOCAL/Frameworks. The bin and lib directories (where >> executables and site-packages) end up will be subdirectories of this. >> You will probably need to point PATH to something like >> $SAGE_LOCAL/Frameworks/Current/bin. > > My sage-env script (of somewhere else) had this: > > # For a framework Python build on OS X, Python's bin directory is not > local/bin > if [ `uname` = "Darwin" ]; then > PATH="$SAGE_LOCAL/Frameworks/Python.framework/Versions/2.5/bin:$PATH" > && export PATH > fi
Thanks for the scripts! I am afraid however, that this is too incompatible with Sage. E.g. once I start doing this in SPD and femhub, any package, like VTK, that works in femhub will *not* work in Sage. And that's bad. So unless Sage itself switches to the framework build, I am afraid I will have to just figure out a fix for VTK to build. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send 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 -~----------~----~----~----~------~----~------~--~---
