The linux and MacOS builds are fairly ready. I'd say Windows is 95% done
(see the other thread). I think we should build all archs in 64bit.
If we go for openbabel channel on anaconda.org we should set it up, then we
could set up Anaconda Cloud builds for linux. For automated builds via CI
some additional scripts should be added to travis for MacOS. Appveyor aslo
needs it's channel and is almost ready on my repo (
https://github.com/mwojcikowski/openbabel-packages/blob/master/appveyor.yml
).
Anyhow we should push updated 2.4.x versions to bioconda/conda-forge. A I
said for Linux and MacOS it's just changing the version in URL, since
current git master compiles.
----
Pozdrawiam, | Best regards,
Maciek Wójcikowski
mac...@wojcikowski.pl
2016-07-05 20:42 GMT+02:00 Geoffrey Hutchison <geoff.hutchi...@gmail.com>:
> > That is fine with me. The beauty of having openbabel channel is that you
> can have "devel" label for current git master and make testing easier.
>
> This sounds great. As a conda user, it would make life much simpler. What
> can I do to help make it happen?
>
> > Other than that I see no reasons not to go with stable builds somewhere
> else as conda-forge/bioconda seam fit for what we try to achieve.
>
> Indeed.
>
> Sounds like there's some resolution. What are the next steps (e.g., what
> would need to change for 2.4.0 or 2.4.1)?
>
> Thanks,
> -Geoff
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbabel-devel
