Goal: build OpenCV 3.1 with Intel 2015b toolchain (as that is the one we have licensed).
We take the existing OpenCV 2.4.9 intel 2014b easyconfig and edit it with the new version and toolchain (after trying with --try-toolchain and failing). This then depends in each of the dependent packages under the new toolchain, so easybuild builds those. During that build process, we discover that some dependencies may have changed. JasPer is looking for libjpeg-turbo, but that is not depended in the JasPer easyconfig, so we add that. CMake is depending on openssl (from the OS!) and cannot find opensslconf.h as it has been moved from /usr/include to /usr/include/x86_64... . So now we have modified at least 3 easyconfigs, and the next step is to depend openssl in CMake so it is not pulled from the OS, and modify the easyconfig for that. This is as far as we have gotten, but there are 8 more dependent packages, not including Python, which I have yet to build successfully - different story. This will lead to what I hope will be a reproducible software build. Am I following the recommended easyconfig workflow here? I assume the default action should be to include dependent packages into easybuild in order to produce the most reproducible easyconfig, right? Also, do the "--try-*" options have the ability to output an easyconfig after the fact if the build was successful? Thanks, Ben McGough System Administrator Center IT/Scientific Computing O 206.667.7818 [email protected] 1100 Fairview Ave. N. P.O. Box 19024 Seattle, WA 98109 Fred Hutch / Cures Start Here fredhutch.org
