Hi GRASS devs,
I’m currently adding new functionalities to the GRASS GIS codebase and need to compile the GRASS binary from source on macOS M1 to test my changes. However, I’m facing several issues with missing dependencies like zstd, proj, pdal, and others. Even after installing these dependencies using Homebrew, the build process still reports them as missing. Additionally, I’m having to manually set the paths for each dependency during configuration, which is quite tedious.
Is there a specific guide or streamlined process for building and compiling GRASS GIS on macOS M1, and is there a recommended approach for automating or simplifying dependency management for the build process?
Additionally, I have to write Python unit tests using the pytest framework. How can I ensure these tests use my local code changes of the GRASS binary rather than the remote or installed version of the code during testing?
Any guidance would be greatly appreciated!
Thank you,
Nishant