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
Whether it goes in the macosx directory, or somewhere else, this will be really useful for us Mac users who would like to have GRASS within their own conda environments. I struggle to compile GRASS on macOS and thanks for putting this together.
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
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.
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
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
(<wenzeslaus@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.Barton@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
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.
I agree. Do you want to start this conversation in a new thread?
With your help, we could try to create a recipe to automatically build a conda package and add it to conda-forge, so the installation would be seamless for other mac users.
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
I know we discussed [2] replacing/updating the text of macosx/ReadMe.md file, but I realised that that particular instruction (however outdated) is related to the whole of the content of that directory (which in turn is presently not functional, reported as issue #457 [3]). So I believe we should leave that directory and the ReadMe as is, until the issue is addressed.
The new wiki pages with instructions for anaconda and macports may perhaps be referenced to in INSTALL file.
Setting up a build script in source for GitHub Actions would be more than welcome(!), but doesn’t contradict the idea of publishing the instructions on wiki.
I think it all reads and links fine now, but it took a lot to get it formatted and linked correctly. Mediawiki is an infuriating variant of standard wiki and markdown.
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
I know we discussed [2] replacing/updating the text of macosx/ReadMe.md file, but I realised that that particular instruction (however outdated) is related to the whole of the content of that directory (which in turn is presently not functional, reported as issue #457 [3]). So I believe we should leave that directory and the ReadMe as is, until the issue is addressed.
The new wiki pages with instructions for anaconda and macports may perhaps be referenced to in INSTALL file.
Setting up a build script in source for GitHub Actions would be more than welcome(!), but doesn’t contradict the idea of publishing the instructions on wiki.
Great work Michael! Please consider putting up a link to the new page at https://grasswiki.osgeo.org/wiki/Compile_and_Install#Mac_OSX.
It would also be good to add categories to the end of the new page (as is the case with its sibling pages):
Done for the first. Need to do the second. Maybe between meetings.
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
I hope someone tries this to see if if works for others.
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