summaryrefslogtreecommitdiffstats
path: root/python/conda
Commit message (Collapse)AuthorAgeFilesLines
* Prepare for python 3.10Willem Jan Palenstijn2021-10-274-1/+15
| | | | We can't (easily) build for python 3.10 yet until cython is available in conda.
* Reorganize docker environmentsWillem Jan Palenstijn2021-10-269-26/+106
| | | | Now using debian8, debian9, debian11 for cuda 8 - 11.4
* Update miniconda version used in docker build environmentsWillem Jan Palenstijn2021-10-263-6/+6
|
* Add brief conda build instructions for win64Willem Jan Palenstijn2021-10-113-0/+27
|
* Update conda packages to python 3.9, cuda 11.1Willem Jan Palenstijn2021-07-017-20/+41
| | | | Since cudatoolkit=11.1 isn't in the main anaconda channel (yet?), the nvidia conda channel is used.
* Restrict conda host env libstdc++-ng to prevent build errors on docker envWillem Jan Palenstijn2021-07-011-0/+2
|
* Minor de-duplicationWillem Jan Palenstijn2021-02-251-2/+4
|
* Fix Windows conda package buildWillem Jan Palenstijn2021-02-251-1/+1
|
* Split conda/cuda build environment in twoWillem Jan Palenstijn2020-11-136-57/+93
|
* Add conda packages for cudatoolkit-11.0Willem Jan Palenstijn2020-10-153-4/+13
|
* Bump conda package versionWillem Jan Palenstijn2020-07-041-1/+1
|
* Use numpy backward binary compatibility for conda packagesWillem Jan Palenstijn2020-02-078-46/+8
| | | | | | | | We now only build a single package built with numpy 1.11.x for numpy>=1.11,<2 . There is no guarantee that every future numpy version covered by this will be compatible with numpy 1.11, but numpy checks this internally at run-time, and should report this (noisily) when this occurs.
* Update python/numpy/cuda versions for condaWillem Jan Palenstijn2020-01-148-10/+19
|
* Increment version to 1.9.9devWillem Jan Palenstijn2019-09-272-4/+4
|
* Use conda compiler toolchain for conda buildsAllard Hendriksen2019-09-209-29/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For both libastra and astra-toolbox: 1) We do not use script_env to set CC/CXX anymore, since the compilers are installed by conda. 2) The build string is made useful by including either the python+numpy version or the cudatoolkit version that the package was built with. 3) Some clean-up of build.sh in buildenv/ For libastra: 1) The libastra.so is built with the conda C/C++ compiler toolchain. This has two benefits: 1) The rpath of libastra.so is set to $ORIGIN, which makes linking easier for dependent packages. 2) libastra.so is linkable against ancient versions of glibc. With old versions of memcpy. 2) The C/C++ compiler version is fixed to 5.4.0 3) In libastra/build.sh, we rename $CONDA_PREFIX to $PREFIX. Apparently, this is how it is supposed to be done. For me, $CONDA_PREFIX was suddenly undefined. Why this was not a problem before, is unclear to me. 4) The cudatoolkit runtime dependency is pinned with pin_compatible 5) The libastra conda package now provides headers and .pc file. This is useful for building C++ packages that depend on astra. 6) Remove some old code related to cudatoolkit<8.0. For astra-toolbox: 1) astra-toolbox uses the conda-provided compilers 2) The compilers are fixed to version 7.3 3) Add boost to host requirements of astra-toolbox Notes on testing: - The libastra build has been tested with all versions of cudatoolkit - The astra-toolbox build has been tested with all provided versions of python after building a single cudatoolkit version of libastra. How to test this branch: - It should work by just editing `python/conda/linux_release/buildenv/build.sh`. Set BRANCH=CI-use-conda-c-compiler-toolchain URL=https://github.com/ahendriksen/astra-toolbox and run release.sh from the `python/conda/linux_release` directory.
* Use recent version of conda during linux conda-buildAllard Hendriksen2019-09-171-1/+8
| | | | | | This fixes the issue where cudatoolkit=8.0 would not install any more with recent versions of conda. Also, no corruption appears to take place while downloading packages.
* Build updates for Debian 8 + CUDA10.1Willem Jan Palenstijn2019-07-084-40/+17
| | | | | | | Debian 7 is EOL, and CUDA 10.1 doesn't support its version of glibc. Hardcoded conda=4.6.14 for now, since 4.7.5 seems to be downloading corrupted packages when running in docker/linux-64.
* Build updates for Win10 + VS2017 + CUDA9 + Matlab R2018bWillem Jan Palenstijn2019-07-086-33/+29
|
* Update conda builds for cuda 10 and numpy 1.16Willem Jan Palenstijn2019-04-128-10/+43
|
* Loosen numpy dependency for conda packageWillem Jan Palenstijn2018-11-011-1/+1
|
* Avoid broken scipy package for testsWillem Jan Palenstijn2018-08-311-0/+2
|
* Drop numpy 1.12/1.13 packagesWillem Jan Palenstijn2018-08-311-2/+0
| | | | Anaconda doesn't have these for python 3.7 apparently
* Build for new cuda/python/numpy versionsWillem Jan Palenstijn2018-08-314-5/+23
|
* Build for numpy 1.14Willem Jan Palenstijn2018-06-011-0/+1
|
* Fix missing version update in conda meta.yamlWillem Jan Palenstijn2017-11-221-2/+2
|
* Update version to 1.9.0devWillem Jan Palenstijn2017-11-222-4/+4
|
* Update version to 1.8.3Willem Jan Palenstijn2017-11-062-6/+6
|
* Add workaround for apparently broken mkl/win-64 conda packageWillem Jan Palenstijn2017-11-061-0/+2
|
* Add libastra/linux-64 conda package variants for cudatoolkitWillem Jan Palenstijn2017-11-0610-55/+130
| | | | Also upgrade the Docker-based linux release scripts to match.
* Update miniconda release for linux conda buildsWillem Jan Palenstijn2017-10-161-1/+1
|
* Update miniconda release for linux conda buildsWillem Jan Palenstijn2017-10-161-3/+3
|
* Fix conda buildWillem Jan Palenstijn2017-03-291-0/+1
|
* Move conda astra-toolbox package files to own subdirectoryWillem Jan Palenstijn2017-03-204-12/+12
| | | | | Recent versions of conda-build (2.1.1 at least) seem to automatically build packages in subdirectories (after the main directory).
* Add autotools and boost to macOS conda libastra dependenciesWillem Jan Palenstijn2017-03-201-0/+4
|
* Silence errors from nvcc test runWillem Jan Palenstijn2017-03-201-1/+1
|
* Change lib/lib64 logicWillem Jan Palenstijn2017-03-201-7/+12
| | | | macOS CUDA uses lib even on 64 bit
* Fix conda boost include flagsWillem Jan Palenstijn2017-03-201-1/+1
|
* Use true instead of /bin/trueWillem Jan Palenstijn2017-03-201-1/+1
| | | | It's in /usr/bin/ on macOS.
* Add np112 to conda build scriptWillem Jan Palenstijn2017-02-241-0/+3
|
* Build conda packages for linux-64/np111/py36Willem Jan Palenstijn2017-01-021-0/+1
|
* Use external boost for conda/win-64Willem Jan Palenstijn2016-12-094-17/+13
| | | | This enables py27 conda packages for win-64.
* Build conda packages for multiple conda versionsWillem Jan Palenstijn2016-12-092-4/+10
|
* Use specific numpy version in conda packageDaniel M. Pelt2016-12-081-1/+1
|
* Update version to 1.8Willem Jan Palenstijn2016-12-052-8/+6
|
* Update versions for 1.8rc1 conda packageWillem Jan Palenstijn2016-12-022-3/+3
|
* Add astra.__version__ (PEP396)Willem Jan Palenstijn2016-12-012-2/+2
|
* Add conda build scripts for win-64/py35Willem Jan Palenstijn2016-12-014-6/+79
|
* Add scripts for building conda packages using DockerWillem Jan Palenstijn2016-12-014-0/+44
|
* Separate C++ and python builds & make conda work nicelyHolger Kohr2016-11-254-23/+40
| | | | | | | | | | | | - make builder (= advanced user or us ourselves) choose compilers and CUDA - add a check for the C++11 flag for nvcc to work around the infamous boost bug if necessary - use conda boost to build the C++ library - simplify python bindings conda recipe to only build the bindings; the C++ library is now a build and runtime dependency - add runtime dependencies to python bindings recipe - some small adjustments to builder.py
* Fix conda build.shWillem Jan Palenstijn2016-11-231-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-28 12:14:59 +0000