On 7/23/07, Green Kobold <[EMAIL PROTECTED]> wrote: > I am trying to make a compiled code out of a sage code that uses > external python libraries like wxpython. The idea is to make this > little experimental app, that uses sage, available for other users. > First, the .spyx run doens't accept "from sage.all import *". Ok, I > took it off, hoping that it would automatically load sage objects. > Than I ran it like: ./sage ../...../FIGUS.spyx. It seems to have > compiled okay. > > There is now a: > home/ref/.sage/spyx/ref-desktop/______python_dev_FIGUS_compiled_FIGUS3_1_spyx > > Can anyone help me with _any_ of these topics: > 1) Is there a way in which I could use the compiled code directly, > running the app outside SAGE, like a standard executable?
No, unless the program hardly uses any of the SAGE library, and you can explicitly extract the relevant code from SAGE for your application. > 2) How can I make this executable installable in other machines, > without requiring users to install SAGE, install external libraries, > and running the .spyx? Unfortunately not. The point of spyx files is *not* to create a standalone application that uses some functionality of SAGE. They exist solely to (1) make it easier to make optimized code, and (2) make it easier to access external C/C++ library code. > If one think it is the case, any suggestion of reading is welcome as well. > > thanks in advance, Feel free to ask further questions, etc. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
