pocmatos
2018-9-11 14:09:24

All, I have been trying to use create-embedding-executable instead of raco exe on the command line and first attempt was a complete failure because my code would not run, the resulting exe looked like a bloated racket, etc. So I looked at the raco exe code.


pocmatos
2018-9-11 14:09:42

I know what most of it is about but I am confused about this line: #:modules (cons (quasiquote (#%mzc: (file ,source-file) (main configure-runtime)))


pocmatos
2018-9-11 14:11:11

What I don’t get is why (#%mzc: ...) and (main configure-runtime). Why is this needed at all?


pocmatos
2018-9-11 14:11:54

Still, even with it I am having issues which I don’t get with raco exe. Currently when I execute my binary I get: no module instance found: #<resolved-module-path:'#%embedded:g849:misc> 0 Have no idea where this comes from.


mflatt
2018-9-11 22:29:08

@pocmatos The #%mzc: is needed so that the embedded main module has a predictable name; that name is used by the #:early-literal-expression and #:literal-expression arguments. The (main configure-runtime) part specifies that those submodules should be included, if they exist. I don’t have a good guess at where the “no module instance found” error comes from, though. Do you have a small-ish example?