On Sunday, July 28, 2019 at 3:48:24 PM UTC+8, james.geddes wrote: > > > My workaround is to tell my colleagues to use homebrew to install Racket; > then use `raco pkg` to install the app; and to specify `(define > racket-launcher-names …)` in the info.rkt file to make an executable.
> It’s a workaround because it requires an additional step beyond this: the > default location for such executables is not typically in one’s PATH, so my > users have to set the PATH. For most of them that’s fine, but for some it’s > not great. > You can always create an executable (using "raco exe") and a distribution (using "raco dist") which packs all dependencies in a single directory. The resulting executable will be stand-alone and will contain all the Racket libraries, including any external packages you use, and will run on computers that don't have Racket installed. You could even sign the resulting executable, if you have a developer certificate. You could also provide a small shell script to update the PATH, which users will have to run once for installation (I believe MacOS stores environment variables in a plist?) The only downside of this approach is that it does not provide a distribution mechanism. But given that you write this program for your colleagues, you could just place the program on an internal network share and tell them to fetch it from there. Alex. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/0db5ce91-919e-41f5-8355-efcecfe4d4b3%40googlegroups.com.
