Thanks, Shu-Hung
With your help, I got it working for the application I was
using this for.
The main thing that made the difference for me was the
(require racket/runtime-path (for-syntax .) thing
and including *a lot* of libs in the call to `raco exe`
I'm still using `load` because I need
#lang racket/load and (load PATH) are less idiomatic and more
low-level in Racket. I don't know how did racket/load and load
interact with ``raco exe'' but here's another way to make it work.
Everything is placed inside modules.
$ racket test.rkt
... ok ...
$ raco exe ++lib
This is some really great advice! Thanks!
I'm still confused about why making an executable isn't working. Am I doing
something wrong?
Even if I choose the framework option for *this* project (it seems like a
really helpful thing)
I'd like to be able to distribute, for example, `.app`
Regarding overriding globals, a Racket `parameter` is more idiomatic:
https://docs.racket-lang.org/reference/parameters.html
And/or, you could load your config file as a module, like `info.rkt` is.
You might find `dynamic-require` and friends interesting:
Hi all!
I read all the documentation and relevant threads (I promise) I could on
the topic but I'm still stuck.
Basically, I'm writing an application that I'd like to be able to read an
"config" file that's valid racket code and can override globals set in the
driver racket module.
Here's a
5 matches
Mail list logo
