#14372: Document ccache better in developer guide
--------------------------------------+--------------------------
Reporter: robertwb | Owner: tbd
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.3
Component: packages: standard | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------------+--------------------------
Changes (by vdelecroix):
* cc: vdelecroix (added)
Comment:
Hi,
(ccing me)
I am against shipping ccache in Sage (following comment:11). On the other
hand, if some OS fails to have it then why not doing the same as gcc? I
have no strong opinion about this as I think that everybody should use a
Unix/GNU distribution (with gcc+ccache available).
Nevertheless, it would be fantastic to document the usage of ccache
- for compiling '''only''' sage source code
- for compiling sage source code and third-party softwares
and I see two places where this might be important
- the Developer guide
- the README
I started using ccache today (thanks to Robert Bradshaw). The only thing I
did is
{{{
$ export PATH=PATH_TO_CCACHE:$PATH
$ sage -b
}}}
Is that the right way to use it? (it seems so as my cache is much bigger
now).
Tell me if I can help for something on that ticket.
Best
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/14372#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
