On 2016-09-11 10:48, Johan S. H. Rosenkilde wrote:
Jeroen Demeyer writes:
https://ccache.samba.org/
And I forgot to mention that I have 2 complete Sage installation trees
so I can let one compile while I use the other.
Thanks, that's useful. Do you need any special setup or care for making
it work in the complicated Sage compilation system, or do you just
override gcc as suggested in the manual?
I am using system-wide ccache and my OS sets up the environment
variables correctly. But a Sage-installed ccache should also "just work".
How much does it speed up
compilation?
A *lot* for everything involving compiling C code. So in the case of the
Sage library, the Cythonizing still needs to be done, but the second
step can be very fast. For packages, the most annoying ones are those
which do a lot of tuning.
Does it ever get clumsy wrt. tracking which tree is in which version and
has which ticket checked out?
Well, there is "git log" or "git status" for that.
I also have two Sage installations, but it's a stable one I use for
work, and a devel one. That way, if devel screws up for whatever reason,
I can still always continue working. I also use it for checking Sage
behaviour without my ticket or if devel is compiling.
In the two Sage trees that I have, I also try to use one as "stable"
release for real work. However, it does not matter much which branch
that one is on (as long as it's not too outdated). If 7.3 works for real
work, then 7.4.beta4 + some unrelated ticket most likely works too.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
