-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document compilation in conda environment #181
Comments
@bryan / @decaluwe ... do either of you have any feedback on building within
works without having to add any configuration options (as long as the conda environment |
I tried this on macOS, and the above steps work well, as does the Python module. However,
Likewise, the C++ sample programs that are installed into the conda environment can be compiled easily, but then fail to run with a similar error. This seems to be a result of SCons not wanting to specify the |
Great to hear that the installation works! But too bad that the library paths aren’t resolved the same way as on Linux and Windows. It’s really surprising that the test suite breaks … certainly didn’t expect that! |
The test issue should be resolved by Cantera/cantera#1229. |
Turns out that there is documentation after all, so it just needs to be updated. |
Resolved via #184. |
Cantera/cantera#1191 introduced some additional simplifications for build processes started from a
conda
environment. While conda-based builds are convenient (and already actively used for the Sundials and windows-2022 runners), this capability is currently undocumented.From a personal perspective, I have working
conda
-based builds on both Linux (Fedora) and Windows. I assume that this will work out-of-the-box on OSX, but do not have the ability to check. Especially on Windows, the installation process is significantly easier than what is currently documented on the website.The text was updated successfully, but these errors were encountered: