|
From: Mojca M. <moj...@gm...> - 2016-03-02 21:43:37
|
On 2 March 2016 at 20:49, Thomas Mattison wrote: > > The motivation for this is mostly for installing gnuplot on Mac's of non-computer-science students. Only one person (like an instructor) would need to download the compiler, download the gnuplot source, build the executables, and create the clone-directory. Everyone else would just copy the clone-directory and run the script inside. > > I realize this would not necessarily work if the student Mac is running a different system version from the instructor. It may be necessary to make a different clone-directory for each OS X system version. But it would only be necessary to do ONCE per version, and not require EVERY student to install the compiler and do the build. > > I also realize that students would still need to install Aquaterm and/or X11, but those have "real" installers so it's not such a big deal. Allin already answered in the same way as I would. I wanted to add that you usually only have to build a binary for the oldest OS and that should automatically work on newer OS versions. But what about using a package manager like MacPorts or Homebrew? You would then get all the dependencies (including AquaTerm, X11, Qt, wxt, pango, cairo, gd, ...) as well a all the updates automatically. In any case I would advise you to try to install the headers and libraries somewhere else than in /usr/local to avoid "messing up" the system. Mojca PS: If someone would write a similar Qt- or wxt-based GUI as the one for Windows (that is: an app that starts with a GUI rather than in a terminal), I would volunteer to create a binary for OS X. The main annoyance is packaging a binary for the terminal. |