#13540: Automatically detect and test optional dependencies.
-----------------------------------+----------------------------------------
       Reporter:  robertwb         |         Owner:  mvngu       
           Type:  enhancement      |        Status:  needs_review
       Priority:  major            |     Milestone:  sage-5.6    
      Component:  doctest          |    Resolution:              
       Keywords:                   |   Work issues:              
Report Upstream:  N/A              |     Reviewers:              
        Authors:  Robert Bradshaw  |     Merged in:              
   Dependencies:                   |      Stopgaps:              
-----------------------------------+----------------------------------------

Comment (by leif):

 Replying to [comment:17 robertwb]:
 > For all intents and purposes, at the moment, gcc really means gcc. And
 building a Cython extension with a different compiler than Python was
 compiled with (and the relevant libraries, for C++ in particular) gets
 really messy.

 We might then even use Python's / distutils' settings for testing tool
 availability (although there's no variable for the Fortran compiler
 AFAIK).  Not sure what to do with bdists (in case they don't contain a
 pre-built GCC as well).

 [[BR]]

 > In any case, the point of this ticket is to introduce a framework that
 lets us test optional doctests automatically, as they the current setup
 means they're never tested and so quickly broken. We could do something
 more sophisticated with CC, etc. but gcc, at the very least, provides a
 common enough dependency to actually exercise this code for most (probably
 all) developers (and it's not near as brittle as others).

 Yes.  Nevertheless, I don't think I'm the only one that almost always sets
 `CC`, `CXX` etc., in order to use ''different versions of GCC''.

 Support for other compilers (e.g. `clang`), probably also flags to pass,
 is certainly out of the scope of this ticket.  (It would be convenient to
 have something like `config.status`, i.e., a mechanism for storing and
 restoring the build environment, and/or also a "`.sagerc`" local /
 specific to the ''Sage installation'', one overriding the other...)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13540#comment:18>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to