Hello,

to avoid recompliation, I am rather doing the following (not sure if this 
is a good thing to do) :

$ git fetch trac    # needs to be in /sage
$ git ch develop        # I switch to the develop branch 
$ git pull trac develop   # this updates to the latest developement version 
of sage
$ make build     # to compile the latest sage
$ git ch develop -b 16325   # creates a new branch, you can choose the name 
as you want
$ git pull trac public/ticket/16325    # applis the branch in trac on top 
of a copy of develop
$ sage -bt whatever

This is merging develop into the branch 16325, so that small changes give 
small compilation time

But one again, maybe this is not an orthodox way..

Le dimanche 11 mai 2014 12:41:24 UTC+2, P Purkayastha a écrit :
>
> Currently, what methods are there to reduce the compilation times during 
> development?
>
> I have a desktop which is not that fast and it takes ages to get sage 
> ready if I change branches. As an example, I ran the following commands
> $ sage -upgrade develop   # this upgraded to sage-6.3.beta0
> $ sage --dev checkout --ticket 16325  # somehow this was not based off 
> develop
> $ git rebase develop      # this rebased the branch ticket/16325 on 
> develop
> $ # made changes to only one file: sage/plot/contour_plot.py
> $ sage -btp --long src/sage/plot
>
> The build took 15 min to complete - it is running the tests now.
>
> I have both ccache and cycache enabled. The last command above identified 
> a lot of files which do not need compilation, but then it also identified 
> over 300 files which needed to be compiled. This is a recurring problem 
> that I face when changing branches and is really time consuming.
>

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to