logos-messaging/libchat
1
0
Fork 0
mirror of https://github.com/logos-messaging/libchat.git synced 2026-03-30 08:03:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
libchat/nim-bindings/conversations_example.nimble

27 lines
547 B
Plaintext
Raw Normal View History

Nim FFI Wrapper for LibChat (#25) * remove unneeded code * Update comment style * Update Nim side to support safer_ffi * Fix Introduction from impl * Updates
2026-01-29 01:38:08 +07:00
# Package
version = "0.1.0"
author = "libchat"
description = "Nim Bindings for LibChat"
license = "MIT"
srcDir = "src"
bin = @["libchat"]
# Dependencies
requires "nim >= 2.2.4"
requires "results"
chore(nim-bindings): replace dynlib dlopen with plain importc (#61) * chore(nim-bindings): replace dynlib dlopen with plain importc The dynlib pragma hard-coded a library path and resolved it via dlopen() at runtime, preventing static linking and forcing a specific load-time path. Using bare {.importc.} lets consumers choose: link liblibchat dynamically at link time (--passL:-llibchat) or link it statically into their binary. * Rust -> Nim ABI (#62) * Use correct build hook * force sret like return from rust code for nim compatibility * Fix target mismatch * Update usages * ci: add nim-bindings-test * fix(nim-bindings): fix ABI mismatch in destroy_* FFI functions and add defer-based cleanup Nim's C backend silently transforms large struct parameters (>16 bytes) into pointer parameters when calling importc functions. The destroy_* functions were declared taking T by value in Rust, but Nim always passed &T — causing Rust to read garbage from the stack on x86-64 (SIGILL on CI) while accidentally working on ARM64 macOS due to that ABI coincidentally also using pointers for large structs. Fix by changing all destroy_* functions to take &mut T and using drop_in_place, which is the correct idiom for dropping a value through a pointer. On the Nim side, replace scattered manual destroy calls with defer, which guarantees cleanup on all exit paths and prevents use-after-destroy bugs. --------- Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
2026-02-25 20:09:55 +01:00
proc buildRust() =
exec "cargo build --release --manifest-path ../Cargo.toml"
Nim FFI Wrapper for LibChat (#25) * remove unneeded code * Update comment style * Update Nim side to support safer_ffi * Fix Introduction from impl * Updates
2026-01-29 01:38:08 +07:00
# Build Rust library before compiling Nim
before build:
chore(nim-bindings): replace dynlib dlopen with plain importc (#61) * chore(nim-bindings): replace dynlib dlopen with plain importc The dynlib pragma hard-coded a library path and resolved it via dlopen() at runtime, preventing static linking and forcing a specific load-time path. Using bare {.importc.} lets consumers choose: link liblibchat dynamically at link time (--passL:-llibchat) or link it statically into their binary. * Rust -> Nim ABI (#62) * Use correct build hook * force sret like return from rust code for nim compatibility * Fix target mismatch * Update usages * ci: add nim-bindings-test * fix(nim-bindings): fix ABI mismatch in destroy_* FFI functions and add defer-based cleanup Nim's C backend silently transforms large struct parameters (>16 bytes) into pointer parameters when calling importc functions. The destroy_* functions were declared taking T by value in Rust, but Nim always passed &T — causing Rust to read garbage from the stack on x86-64 (SIGILL on CI) while accidentally working on ARM64 macOS due to that ABI coincidentally also using pointers for large structs. Fix by changing all destroy_* functions to take &mut T and using drop_in_place, which is the correct idiom for dropping a value through a pointer. On the Nim side, replace scattered manual destroy calls with defer, which guarantees cleanup on all exit paths and prevents use-after-destroy bugs. --------- Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
2026-02-25 20:09:55 +01:00
buildRust()
Nim FFI Wrapper for LibChat (#25) * remove unneeded code * Update comment style * Update Nim side to support safer_ffi * Fix Introduction from impl * Updates
2026-01-29 01:38:08 +07:00
task pingpong, "Run pingpong example":
chore(nim-bindings): replace dynlib dlopen with plain importc (#61) * chore(nim-bindings): replace dynlib dlopen with plain importc The dynlib pragma hard-coded a library path and resolved it via dlopen() at runtime, preventing static linking and forcing a specific load-time path. Using bare {.importc.} lets consumers choose: link liblibchat dynamically at link time (--passL:-llibchat) or link it statically into their binary. * Rust -> Nim ABI (#62) * Use correct build hook * force sret like return from rust code for nim compatibility * Fix target mismatch * Update usages * ci: add nim-bindings-test * fix(nim-bindings): fix ABI mismatch in destroy_* FFI functions and add defer-based cleanup Nim's C backend silently transforms large struct parameters (>16 bytes) into pointer parameters when calling importc functions. The destroy_* functions were declared taking T by value in Rust, but Nim always passed &T — causing Rust to read garbage from the stack on x86-64 (SIGILL on CI) while accidentally working on ARM64 macOS due to that ABI coincidentally also using pointers for large structs. Fix by changing all destroy_* functions to take &mut T and using drop_in_place, which is the correct idiom for dropping a value through a pointer. On the Nim side, replace scattered manual destroy calls with defer, which guarantees cleanup on all exit paths and prevents use-after-destroy bugs. --------- Co-authored-by: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
2026-02-25 20:09:55 +01:00
buildRust()
exec "nim c -r --path:src --passL:../target/release/liblibchat.a --passL:-lm examples/pingpong.nim"
Reference in New Issue Copy Permalink