successfully called Racket CS from C. I'll try what you suggest re calling
C from Racket at some point and report any problems.
Thank you!
On Sunday, 29 March 2020 21:41:46 UTC+1, Matthew Flatt wrote:
>
> At Sun, 29 Mar 2020 13:13:08 -0700 (PDT), zeRusski wrote:
> > First, CS snapshots in Utah
At Sun, 29 Mar 2020 13:13:08 -0700 (PDT), zeRusski wrote:
> First, CS snapshots in Utah and NW mirrors offer no libracketcs.a so I went
> ahead and attempted to build CS from the github master. Sadly its `raco`
> tool is unaware of the `ctool` subcommand, so I'm guessing snapshots are
> built fr
>
> It wouldn't work anyway since `declare_modules` also failed to resolve
> and I'm guessing I really need the `libracketcs.a` from the snapshot for
> that.
>
Oh ... I see `declare_modules` is produced by `raco ctool`. Why static
though? This means I have to #include "hello.c" like in the ex
Failed so far, sigh.
First, CS snapshots in Utah and NW mirrors offer no libracketcs.a so I went
ahead and attempted to build CS from the github master. Sadly its `raco`
tool is unaware of the `ctool` subcommand, so I'm guessing snapshots are
built from your own private fork or something. I the
At Fri, 27 Mar 2020 15:48:13 -0700 (PDT), zeRusski wrote:
> How I might go about embedding Racket CS
The current development version (as reflected by snapshot builds) now
has support and documentation for that:
https://www.cs.utah.edu/plt/snapshots/current/doc/inside/cs-embedding.html
Of course
How I might go about embedding Racket CS in a fairly big C codebase, about
100KLOC big. It is exceptionally well written C authored by people who knew
what they were doing. I am sadly not one such person, so I'd rather not
muddy things with my exceptionally terrible C. C code will be driving the
6 matches
Mail list logo
