#12659: build the sage library in place
-------------------------------+-----------------------------
       Reporter:  mhansen      |        Owner:  GeorgSWeber
           Type:  enhancement  |       Status:  needs_work
       Priority:  major        |    Milestone:  sage-6.3
      Component:  build        |   Resolution:
       Keywords:               |    Merged in:
        Authors:  Mike Hansen  |    Reviewers:  William Stein
Report Upstream:  N/A          |  Work issues:
         Branch:               |       Commit:
   Dependencies:  #13363       |     Stopgaps:
-------------------------------+-----------------------------

Comment (by nthiery):

 As I mentionned on sage-devel, I recently noticed some preliminary
 work in src/setup.py toward compiling the Sage library in place,
 instead of putting the produced .so and copies of the .py files in
 src/build.

 Compiling in place means saving 15s of `sage -b` each time I just
 modify Python code, and I do that all the time; so we are speaking of
 dozen of minutes per day. So I have been dreaming of it for
 years. Besides, it would also remove one of the regular source of
 confusions for our new contributors.

 So I explored this further, and with very minimal further changes ,
 this apparently seems to work smoothly: I haven't yet run all tests,
 but Sage starts, the documentation compiles, etc.

 See branch u/nthiery/compile_library_inplace:

 http://git.sagemath.org/sage.git/commit/?h=u/nthiery/compile_library_inplace

 I can't wait until I can use this for real Sage development. But for
 this, I basically need to get this feature into Sage. It would be
 adventurous to enable this feature by default for all users at this
 point. On the other hand, we should allow the adventurous of us to use
 this extensively to chase out the bugs.

 What would be the right approach to make this feature configurable
 when one compiles Sage for the first time? Using just an environment
 variable set by the user is not good, since a given user might have
 Sage installations configured differently. Some piece of information
 must be stored somewhere at configuration time.

 I am happy to use a different ticket for this if this is deemed
 preferable.

 Cheers,
                          Nicolas

--
Ticket URL: <http://trac.sagemath.org/ticket/12659#comment:41>
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.

Reply via email to