Fixes to help with conda-forge builds

[speth]

Changes proposed in this pull request

Fixes to resolve issues encountered while trying to update the conda-forge recipe (see conda-forge/cantera-feedstock#27), plus (unrelated) removal of a few unnecessary declarations.

• Relax tolerance on test_phase_order_surf_jacobian, which was failing by a slim margin on ppc64le Linux builds
• Fix OpenMP flags in generated CMakeLists.txt files -- see https://gitlab.kitware.com/cmake/community/-/wikis/doc/cmake/VariablesListsStrings for some help understanding the rather non-intuitive CMake syntax.
• Implement workaround in sample SConstruct files for SCons ignoring RPATH on macOS
• Improve setting compiler in sample SConstruct files: do not set a default compiler for "package" builds, and allow the user to override using standard environment variables such as CXX
• Always allow the conda layout when using package_build
• Check return value of soln_newSolution in clib demo to avoid undefined behavior if the input file is not found
• Search the active conda environment for YAML files
• Fix cleanup of -isysroot flags in package builds
• Remove declaration for the method MultiTransport::correctBinDiffCoeffs which had no corresponding implementation
• Remove friend declarations from DenseMatrix -- these methods either don't exist with the specified signature (invert) or only access public members of the DenseMatrix class (solve) and don't need to be friends.

Checklist

• [x] The pull request includes a clear description of this code change
• [x] Commit messages have short titles and reference relevant issues
• [x] Build passes (scons build & scons test) and unit tests address code coverage
• [x] Style & formatting of contributed code follows contributing guidelines
• [x] The pull request is ready for review

[ischoegl]

There is another tolerance issue in #1271 (which was resolved by patching downstream) - I'd consider adopting this for the same rationale as provided here for conda-forge?

[speth]

I stand by my comment in that PR, and don't think the patch proposed there should be adopted as our baseline. It's not even clear at this point whether that patch is still necessary on those systems, or whether it was just a transient due to specific builds of g++ and/or glibc.

[ischoegl]

I stand by my comment in that PR, and don't think the patch proposed there should be adopted as our baseline. It's not even clear at this point whether that patch is still necessary on those systems, or whether it was just a transient due to specific builds of g++ and/or glibc.

Sure. I was mainly asking as the tolerance adjustment was pretty minor, going from rtol = 1e-14; to rtol = 1.2e-14; - see proposed change. I'm fine either way, but I thought I'd bring it up. PS: It is true that it is no longer clear whether this is needed any longer, and it probably shouldn't change under those circumstances.

[codecov[bot]]

Codecov Report

Merging #1591 (c85fdb5) into main (cde1e79) will decrease coverage by 0.03%. Report is 2 commits behind head on main. The diff coverage is 16.66%.

:exclamation: Current head c85fdb5 differs from pull request most recent head 2ba2cb0. Consider uploading reports for the commit 2ba2cb0 to get more accurate results

@@            Coverage Diff             @@
##             main    #1591      +/-   ##
==========================================
- Coverage   70.61%   70.58%   -0.03%     
==========================================
  Files         379      379              
  Lines       59153    59169      +16     
  Branches    21252    21257       +5     
==========================================
- Hits        41768    41762       -6     
- Misses      14311    14331      +20     
- Partials     3074     3076       +2     

Files Changed	Coverage Δ
include/cantera/numerics/DenseMatrix.h	100.00% <ø> (ø)
include/cantera/transport/MultiTransport.h	50.00% <ø> (ø)
samples/clib/demo.c	77.77% <0.00%> (-19.90%)	:arrow_down:
src/base/application.cpp	59.51% <42.85%> (-0.99%)	:arrow_down:

... and 1 file with indirect coverage changes

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more