Replies: 4 comments 2 replies
-
|
Hi! Sorry about the late response -- somehow I missed your message until now. (Might have something to do with being on parental leave last summer...) MacPorts-based instructions in the manual are from a few years back, when I used a Mac. I no longer use a Mac to work on PISM, so unfortunately I cannot easily update that section or test if it is up to date. I'll see what I can do, though. |
Beta Was this translation helpful? Give feedback.
-
|
Note that for testing OS X stuff on Linux I have found this 1-button OS X in Virtualbox script to provide a working setup: https://github.com/myspaghetti/macos-virtualbox |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
It helps non-OS X developers test it, which helps OS X users. |
Beta Was this translation helpful? Give feedback.
-
|
Setting up a macOS VM turned out to be too much of a pain, but I still made some progress. Now we can install PISM 2.1 on macOS by running Run To install tools and libraries required to build PISM, run I will update PISM's Homebrew formula and the manual for the 2.1.1 bug fix release. |
Beta Was this translation helpful? Give feedback.
-
Hello! tl;dr: mac instructions should mention homebrew commands
Long story: I am helping a scientist install PISM on a Mac laptop. I run Debian on my machines and don’t use Macs, but I get a strong impression from other people (Python core developers, contributors and other Python developers) that Homebrew is the preferred developer tool to install system libraries. So we took the instructions written for Macports and translated the package names to Homebrew, and could successfully install the PISM dependencies as well as Petsc (from homebrew too, not from source).
On one Mac laptop, running cmake (with CC options but no install prefix) then make worked straight up, but on another one the auto-detection didn’t happen and cmake errored out with a message about PETSC_LIB and PETSC_ARCH, which we didn’t have to set on the other machine.
It would be very appreciated if we could get help on how to let cmake find the Petsc installed by Homebrew.
And I think it would benefit even more people if the docs moved from Macports instructions to Homebrew 🙂
Beta Was this translation helpful? Give feedback.
All reactions