#6743: cygwin metaticket: port Sage to Microsoft Windows (via Cygwin): stage 1 
--
make building Sage automatic
-----------------------------------+----------------------------------------
       Reporter:  was              |         Owner:  was                        
                                                                       
           Type:  enhancement      |        Status:  needs_info                 
                                                                       
       Priority:  major            |     Milestone:  sage-5.9                   
                                                                       
      Component:  porting: Cygwin  |    Resolution:                             
                                                                       
       Keywords:  sd31 sd32        |   Work issues:                             
                                                                       
Report Upstream:  N/A              |     Reviewers:  Jean-Pierre Flori, Dmitrii 
Pasechnik, Karl-Dieter Crisman, Mike Hansen, William Stein, Luis Tabera
        Authors:                   |     Merged in:                             
                                                                       
   Dependencies:                   |      Stopgaps:                             
                                                                       
-----------------------------------+----------------------------------------

Comment (by leif):

 Replying to [comment:225 jpflori]:
 > Replying to [comment:224 jpflori]:
 > > Replying to [comment:222 leif]:
 > > > Replying to [comment:221 jpflori]:
 > > > > Strange that the fact $SAGE_LOCAL/bin is in $PATH is not
 sufficient but whatever.
 > > > > And not sure why in sage-enc $SAGE_LOCAL/lib is appended rather
 than prepended.
 > > > > I mean, were prepending $SAGE_LOCAL/bin, so...
 > > >
 > > > ? In both cases (`PATH` as well as `LD_LIBRARY_PATH`), directories
 get '''pre'''pended (provided they exist).
 > > It seems PATH is not, in sage-env:
 > > {{{
 > > export PATH="$SAGE_PACKAGES/bin:$SAGE_LOCAL/bin:$PATH"
 > > }}}
 > And I think it's normal.
 > We want Sage binaries to be found first.
 >
 > As far as [LD_]LIBRARY_PATH is concerned, I wouldn't find it so
 disturbing to prepend SAGE local dirs as well.
 >
 > But note that PATH is usually set (or the shell used might not be so
 useful) whereas [LD]_LIBRARY_PATH is not.
 > So prepending our local values in the first case is really the most
 sensible choice, whereas in the second you might think that the user has
 added something unusual knowingly and he wants it first, if that breaks
 that's his problem.

 I still don't understand what you mean.  In both cases, we already prepend
 ''Sage's'' directories, such that Sage's shared libraries and binaries
 come first.

 (That's orthogonal to putting DLLs into `*/bin/` or adding DLL dirs to
 `PATH` on Cygwin.  Note that IIRC we already do the former for some
 packages, so if you add `$SAGE_LOCAL/lib/` to `PATH` as well, we IMHO
 should no longer copy DLLs into `$SAGE_LOCAL/bin/`.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6743#comment:228>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to