- 
                Notifications
    You must be signed in to change notification settings 
- Fork 640
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Use case
Currently, developers on macOS face significant challenges when setting up a local development environment to compile the gitextractor plugin.
Building plugin gitextractor to bin/plugins/gitextractor/gitextractor.so with args:   --gcflags=
# github.com/libgit2/git2go/v33
../../../../go/pkg/mod/github.com/libgit2/git2go/[email protected]/Build_system_dynamic.go:12:3: error: "Invalid libgit2 version; this git2go supports libgit2 between v1.3.0 and v1.3.0"
   12 | # error "Invalid libgit2 version; this git2go supports libgit2 between v1.3.0 and v1.3.0"
      |   ^
1 error generated.
make[2]: *** [build-plugin] Error 1
make[1]: *** [godev] Error 2
make: *** [godev] ErrorThe primary issue is related to compilation failures and dependency conflicts related to git2go. Many macOS developers use Homebrew to manage packages, and Homebrew often installs its own version of libgit2 as a shared dependency for other tools. This system-level installation frequently conflicts with the version required by the plugin, forcing developers into complex workarounds.
This creates a high barrier to entry for new contributors and makes the development process unnecessarily frustrating.
A PR was merged some time ago introducing devcontainers, which works as expected and would kindly ask to bring this back (special thanks to @TonyWu1995 )
Description
No response
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct