sorry to necro/hijack this thread. hey, @ward how can I get in touch?
I re-read [The Nim memory model](https://zevv.nl/nim-memory/) and I think I see
why the first example wouldn't have worked (when the stack unwinds `addr e` no
longer points to `e`).
I updated the example @shirleyquirk provided but I still have a read from nil
error. This is confusing because `c
I'm trying to use Nim's FFI to import a proc from a compiled Nim library that
returns an object `Foo`. I want to create a `Foo` object from the pointer
returned by this imported proc.
I get an illegal storage access error. This seems like it should be simple,
what am I doing wrong?
This is really cool. Would be great if it included a start up script to install
nimble packages too.
MinGW is creating this path somehow.
Yep, the csources are there.
I'm new to MinGW so I'm not sure how to fix that path issue. If this were a
case of MinGW incorrectly building a path then I would expect it to be a common
problem for anyone cross-compiling with a wrapped c library. Unfortunately I'm
not turning up more info on wha
ecls.nim\csources\src\codec\ccopy
CC: decls.nim\csources\src\codec\dec16be
CC: decls.nim\csources\src\codec\dec16le
CC: decls.nim\csources\src\codec\dec32be
x86_64-w64-mingw32-gcc: error:
/home/VVX7/.nimble/pkgs/bearssl-0.1.5/bearssl/decls.nim\csources\src\codec\ccopy.c:
No such file
