Lori A. Burns

If it works cmake-side, conda-build shouldn't be a dealbreaker. The one note I found suggests I got the build to the point where a bzip2 gave up for other too-big-AM...

Second the "simply awful" appraisal. But I can't imaging supporting Windows, ilp64, all combinations of static, cdft, etc. to replace the CMake one. Slightly off-topic for autocmake, but the fall-back...

fyi https://gist.github.com/multiplemonomials/6ee074038778a21cd25b73659a6a82d9

a thought on matching math detection to a pre-built numpy. preserving the comment here. https://github.com/psi4/psi4/pull/1031#discussion_r192517976

This is where changes spill over from the build system to the code. I'd consider renaming `HAVE_OPENMP` more disruptive than where the openmp_flags go among the cmake vars. For the...

I don't particularly care, as I'll probably stick with the file in psi4/psi4#1017. The suggestion in @robertodr's 3rd paragraph, while nominally very sensible, would bring psi back to the original...

By the way, I started sketching out how I'd want math detection to properly interact with the new capabilities of `FindOpenMP.cmake`, with the primary complication being that compiler/blas distribution/omp are...

I'm on cmake 3.9.4 and gcc 7.2.0 (from conda). conda gfortran isn't providing `omp_lib` header or module, so that's probably why kitware findopenmp is failing to detect for Fortran, which...

Yes, I was just going to ask if there'd be forseeable trouble with `if(${OPENMP_FOUND} OR ${OpenMP_C_FOUND})` per-language? I don't know what cmake wants in the way of quotes these days.

I'll experiment with those lines, thanks. I'm a huge fan of the imported target in general. But I don't dare do it here b/c of the problem I was discussing...