-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Everywhere we were allowing use of jinja2 compilers from conda-forge, supply a pinned default instead. This insures our packages are compatible with each other. When moving away from jinja templated compilers, I found we are not including enough. *compilers*_arch package is necessary. For example: ```pre conda install gcc cmake dosomething ``` ...may fail with Cmake not able to discover where/how to use GCC. SEACAS contrib example: ```pre -- The C compiler identification is unknown CMake Error at cmake/tribits/core/package_arch/TribitsGlobalMacros.cmake:1462 (enable_language): No CMAKE_C_COMPILER could be found. ``` `conda install gcc gcc_linux-64`, is the proper way (or rather, more proper than without it). As with all things conda-build, I am still learning. SEACAS build.sh change: Supply lib directory when building SEACAS. There seems to now be an issue with contribs being installed in `lib64` while Conda still expects things in `lib`. This is the bit I am referring to when I say "or rather, more proper than without it" above. Before this change, telling Cmake were libs go was not necessary...
- Loading branch information
Showing
7 changed files
with
70 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters