You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In order to improve the ease of use/installation of Topiary, I believe it would be good to provide compiled binaries for common architecture with each release. This would allow random users to just download and run Topiary.
More importantly, this would open the door to easy distribution as a package, because this would not require any more compilation from the package maintainers. This could allow distribution through OPAM, for instance, or alternative faster distribution through nixpkgs (which, for now, contains only the version of Topiary one needs to compile).
These considerations came up in the context of #254.
The text was updated successfully, but these errors were encountered:
+1 for this. Also, Windows binaries would be very welcome (incidentally, if distributing binaries it would be good to keep the option of statically linking the tree-sitter grammars in order to keep the distributed binaries self-contained, cf #4).
Is your feature request related to a problem? Please describe.
In order to improve the ease of use/installation of Topiary, I believe it would be good to provide compiled binaries for common architecture with each release. This would allow random users to just download and run Topiary.
More importantly, this would open the door to easy distribution as a package, because this would not require any more compilation from the package maintainers. This could allow distribution through OPAM, for instance, or alternative faster distribution through nixpkgs (which, for now, contains only the version of Topiary one needs to compile).
These considerations came up in the context of #254.
The text was updated successfully, but these errors were encountered: