On a more general note — it seems to be a good idea to completely
reorganize GRASS source tree structure for G8. I have already added it
to the list of G8 ideas:
https://trac.osgeo.org/grass/wiki/Grass8Planning#Codeorganisationcodingstyles
At the moment we have actual source intermingled with compilation and
packaging related stuff and with every new way how to deliver GRASS it
gets only worse. Feel free to add your ideas on potential new source
tree layout to the trac.

Māris.

piektd., 2020. g. 29. maijs, plkst. 04:14 — lietotājs Vaclav Petras
(<wenzesl...@gmail.com>) rakstīja:
>
> 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.bar...@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@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to