[GRASS-dev] where to make compiling instructions available

[Vaclav Petras]

A script in the source code preferably executed in GitHub Actions seems
like a good place for a build of a primary distribution for macOS. It would
not only show which latest change to the source code breaks the build, but
it would also clearly show that the script itself works over and over again
in at least one environment.

Vaclav

On Wed, May 27, 2020 at 5:19 PM Michael Barton <Michael.Barton at asu.edu>
wrote:

> I've put together a step by step guide to compiling Mac binaries, using
> Anaconda. Because it uses Anaconda, it probably does not belong in the
> source code (though it might help someone create instructions for the
> source code). However, it would probably be helpful to at least some
> people. Any suggestions as to where I should put this?
>
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social &
> Ecological Sciences
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: 'http://www.public.asu.edu/~cmbarton,
> https://complexity.asu.edu/csdc'
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20200528/bce97c24/attachment.html>