These are chat archives for symengine/symengine

26th
Jul 2016
Spencer Lyon
@sglyon
Jul 26 2016 08:46
@isuruf I think that using Conda.jl to provide the binary should be really easy given that you already have things on conda-forge
That’s very exciting. One hesitation I had with adopting SymEngine.jl in my new project was that installation isn’t trivial (I just build my own dylib by hand instead of using the build.jl script). If we can get the conda install to run smoothly this concern is gone!
Isuru Fernando
@isuruf
Jul 26 2016 08:48
Is there a option to say which version of the package from conda to use? This is the only concern I have for now
Btw, did build.jl script fail?
Spencer Lyon
@sglyon
Jul 26 2016 08:49
I haven’t used Conda.jl in my own projects, but I would imagine that you can.
I can’t recall if the build script failed or not. I was playing with the C++ code so I was building it on my own anyway and just reused the shared lib
Isuru Fernando
@isuruf
Jul 26 2016 08:50
Okay. using Conda.jl would enable windows builds as well
Also, the conda packages have optional dependencies installed as well. (MPFR for big floats and MPC for big complex floats)
Spencer Lyon
@sglyon
Jul 26 2016 08:52
Oh that’s really cool. Yep, seems like a clear winner imo
Isuru Fernando
@isuruf
Jul 26 2016 09:12
@asmeurer, right now the python-symengine conda package is 0.1.0.dev0+97c5a21. When I update the package to say, 0.1.0.dev0+0bcdefg where 0bcdefg is a newer hash than 97c5a21, what would conda consider as the newst version?