Using the build variant feature of conda-build 3.0+ (as well as compiler support) we can speed up the process of building the library and make it architecture independent.
The c and c++ compilers provided by anaconda are used on MacOS and Linux, and (once we finish building on windows) it will handle the build specifications. In order to allow for this, a few cmake parameters had to be tweaked (see PR https://github.com/vmtk/vmtk/pull/207).
For MacOS, the MacOSX10.9-SDK has to be available on the system path (currently set to /opt/MacOSX10.9.sdk). It can be downloaded from https://github.com/phracker/MacOSX-SDKs.
Benefits of the system include:
Much simpler commands to build the library.
Automatic pinning of dependency versions which guarantee API/ABI compatibility.
Easy transition to conda-forge once they move to conda-build 3.0+ (the issue with slow "fixing linking" on the mac has been solved.
this is a work in progress. need to document and ensure everything works before moving forward.
Using the build variant feature of conda-build 3.0+ (as well as compiler support) we can speed up the process of building the library and make it architecture independent.
The c and c++ compilers provided by anaconda are used on MacOS and Linux, and (once we finish building on windows) it will handle the build specifications. In order to allow for this, a few cmake parameters had to be tweaked (see PR https://github.com/vmtk/vmtk/pull/207).
For MacOS, the MacOSX10.9-SDK has to be available on the system path (currently set to /opt/MacOSX10.9.sdk). It can be downloaded from https://github.com/phracker/MacOSX-SDKs.
Benefits of the system include:
this is a work in progress. need to document and ensure everything works before moving forward.