CVXOPT has no dependencies on Numpy (but can exchange data with Numpy arrays efficiently via a buffer protocol).
On Jul 15, 11:04 am, François Bissey <f.r.bis...@massey.ac.nz> wrote: > > On 07/14/10 10:58 PM, Nathan Dunfield wrote: > > >> On a similar note cvxopt can make use of glpk as well. > > > > Yes, it can --- I was just using this yesterday. > > > > The trick is that you have to tell cvxopt that glpk is available when > > > it is compiled/installed. Now that glpk is standard, the install > > > script for cvxopt should be told to make use of it. You just need to > > > edit a couple of lines in setup.py to make this happen. Has this > > > already been done, or should I file a patch for this? > > > > Best, > > > > Nathan > > > I strongly suspect you would also need to make sure glpk builds before > > cvxopt by editing spkg/standard/deps. The cvxopt entry would then look > > like this. > > > $(INST)/$(CVXOPT): $(BASE) $(INST)/$(FORTRAN) $(INST)/$(F2C) \ > > $(INST)/$(LAPACK) $(INST)/$(BLAS) $(INST)/$(NUMPY) \ > > $(INST)/$(ATLAS) $(INST)/$(CEPHES) $(INST)/$(GLPK) > > > If you wanted to use the GLPK library in R, then the R entry would need to > > be modified by adding the "$(INST)/$(GLPK)" on the end too. > > > You might find it works without doing the above, but unless you specify the > > build order, it will be semi-random, especially with parallel builds. > > Just checked the source, it is definitely a build time dependency so > this is needed otherwise the build will fail. > However as far as I can see cvxopt shouldn't depend on numpy (unless > that's a change between version 0.9 and 1.1). > > Francois -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
