> So, where does this leave giac? You're probably no going to find > someone currently involved with Sage who wants to work on it with you. > If you want to further its incorporation into Sage, here's what you > can do. The first step would be making giac an experimental spkg. > Personally, I know very little about the process for doing so: I've > tended to work mostly within the Sage library of Python and Cython > code. But if you log on to the #sage-devel IRC channel you will > likely find someone who can answer questions as they come up. In > particular, I don't think an experimental spkg requires any Python > code. >
I just tried to compile the latest source of giac on sage.math.washington.edu with what seems to be the standard method sage -sh ./configure --prefix="$SAGE_LOCAL" --disable-gui It works. What is now required to make an experimental spkg? What should I do with a spkg? > The second step is to take a look at how Sage interfaces with outside > software. Look through the files in sage.interfaces for examples of > using pexpect to communicate with running instances of other programs > (this is how sage communicates with maxima). Since giac is written in > C++, you can also link to it dynamically and make the functionality > available through Cython. This tends to be significantly more work > than just writing a pexpect interface. Take a look at the wrappers in > sage/libs and the C and C++ code in c_lib for some examples of Sage > using other programs as libraries (eg pari, ntl, mwrank, flint...). > That is the part where someone who knows about sage and/or python is most probably required. > Next, one would make the experimental spkg into an optional one by > making sure that it builds on the platforms Sage supports. Then the natural question is how do I get access to a platform where it would not build in order to fix things? > 2. The package must build on our supported architectures: > * Linux x86, x86_64, itanium, ppc > * OS X ppc, intel > * Solaris sparc, x86_64 > * MS Windows (or at least a reasonable plan for building in > the near future) > > At every stage of this process, you should be able to find help in > answering questions that come up. Whether you can find someone else > to chip in and contribute to the work depends on who else is excited > about getting giac into Sage. But you should feel free to go ahead > and go through the steps of making giac an optional spkg even if > nobody currently involved in Sage development is enthusiastic enough > to help out. If it's important enough to you to put in the work, go > for it! > David Thanks for your message! --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
