[GRASS-dev] Automatic/CI compilation on macOS
n_larsson at yahoo.com
Tue Sep 22 02:02:37 PDT 2020
The "grass-conda" build repo has the potential to be able to automatically (e.g. with GitHub Artefact) create release packages. I’m working on eliminating/limiting the number of patches needed.
Initially I was thinking in lines of creating a repo under https://github.com/OSGeo, but a slimmed down version (of "grass-conda") could also be incorporated in GRASS source repo.
A conda based Mac build test on CI wouldn’t hurt, but in my experience the major difference (vs. Linux, Win) lies in GUI, which is not tested.
Re: python executable – on mac python needs to be installed as framework, else "RuntimeError: Python is not installed as a framework.” The python.app is a workaround/wrapper for that, as conda installs standard unix-like python.
> On 15 Sep 2020, at 05:23, Vaclav Petras <wenzeslaus at gmail.com> wrote:
> Hi Nicklas,
> Thanks, these look great. What do you suggest as next steps?
> It would be great to have at least one of these running in the main repo. I don't know if we need all, but each has its specifics. An App bundle would make sense as a test of a primary way of distributing. (There is a lot of additional code in grass-conda repo, but we do have a ton of code for Windows packaging in the repo.) Plain build inside conda would be nice and simple for the testing purposes. An actual conda package build, possibly cross-platform in the future, sounds like the right thing to do since conda is already involved.
> BTW, I merged your Install.make fix. Please, consider doing more of these. "enable OSX Help Viewer" and other macOS-only cases should go to the main code rather than being a patch. The PYTHON var (Python executable (which is used for ?)) would make sense as something configurable.
More information about the grass-dev