Callback functions from Rust to Go
I'm trying to create the possibility to call a rust function from go and then said rust function calls back the function to go. I'm using cgo as the ffi interface between go and rust. The following is my go code (src/main.go):
package main import ( "c" "fmt" "unsafe" ) /* #cgo cflags: -i./../lib #cgo ldflags: -l./../bin -lgo_move -wl,-rpath=./bin #include "move.h" */ //export cosmoscallbackwrapper func cosmoscallbackwrapper(data *c.uchar, datalen c.int) { // convert data to go slice godata := c.gobytes(unsafe.pointer(data), datalen) // call the actual callback function cosmoscallback(godata) } // setcosmoscallback sets the callback function to be called by the move vm. func setcosmoscallback(callback func([]byte)) { cosmoscallback = callback c.set_cosmos_callback((c.cosmos_callback)(unsafe.pointer(c.cosmoscallbackwrapper))) } var cosmoscallback func([]byte) func main() { // create a new move interpreter // set the callback function setcosmoscallback(func(data []byte) { fmt.println("received data from move vm:", data) // handle data and call cosmos sdk functions as needed }) }
This is my rust code (src/lib.rs)
use std::os::raw::{c_char, c_int}; use std::ffi::cstring; use std::sync::mutex; #[macro_use] extern crate lazy_static; pub fn main() { } pub type cosmoscallback = extern "c" fn(*const c_char, c_int); lazy_static! { static ref callback: mutex<option<cosmoscallback>> = mutex::new(none); } #[no_mangle] pub extern "c" fn set_cosmos_callback(callback: cosmoscallback) { let mut cb = callback.lock().unwrap(); *cb = some(callback); } #[no_mangle] pub extern "c" fn cosmoscallbackwrapper(data: *const c_char, data_len: c_int) { let cb = callback.lock().unwrap(); if let some(callback) = &*cb { callback(data, data_len); } }
This is my cargo.toml file:
[package] name = "go-move" version = "0.1.0" edition = "2021" [lib] crate-type = ["cdylib"] [dependencies] libc = "0.2" lazy_static = "1.4.0" [workspace] members = [ ".",]
This is lib/move.h (header file of shared library):
#ifndef move_vm_lib_h #define move_vm_lib_h #include <stdint.h> //typedef void (*cosmos_callback)(const unsigned char *data, int data_len); //void set_cosmos_callback(cosmos_callback callback); typedef void (*cosmos_callback)(const uint8_t* data, int32_t data_len); void set_cosmos_callback(cosmos_callback callback); #endif
This is my makefile:
shell := /bin/bash .phony: build os = $(shell uname) clean: rm -rf bin rm -rf target build: @echo the os is $(os) mkdir bin cargo build --release ifeq ($(os),linux) cp target/release/libgo_move.so bin/ else cp target/release/libgo_move.dylib bin/ endif cp -a lib/. bin/ go build --ldflags="-l./bin -lgo_move" -o bin/main src/main.go run: export ld_library_path=./bin && ./main
The file structure is as follows:
src main.go main.rs bin libgo_move.so (after cargo build) lib move.h cargo.toml makefile
After running make clean build
I get the following output:
cp target/release/libgo_move.so bin/ cp -a lib/. bin/ go build -o bin/main src/main.go # command-line-arguments src/main.go:27:59: could not determine kind of name for C.cosmosCallbackWrapper src/main.go:27:25: could not determine kind of name for C.cosmos_callback src/main.go:27:2: could not determine kind of name for C.set_cosmos_callback
For some reason it can't find the ffi function.
Correct answer
This is a stupid mistake:
/* #cgo CFLAGS: -I./../lib #cgo LDFLAGS: -L./../bin -lgo_move -Wl,-rpath=./bin #include "move.h" */
Must be done before importing. That's all.
The above is the detailed content of Callback functions from Rust to Go. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

typedef struct is used in C language to create structure type aliases to simplify the use of structures. It aliases a new data type to an existing structure by specifying the structure alias. Benefits include enhanced readability, code reuse, and type checking. Note: The structure must be defined before using an alias. The alias must be unique in the program and only valid within the scope in which it is declared.

When using function pointers in C++, memory management must be carefully considered to avoid pitfalls. These traps include dangling pointers (pointing to functions outside their scope) and wild pointers (function pointers that are never initialized or set to nullptr). To avoid these pitfalls, follow these best practices: always initialize function pointers, manage memory carefully, and use smart pointers. This way you can use function pointers safely and avoid falling into pointer traps.

The use of typedef is to create new aliases for existing data types. Using typedefs can increase the readability and maintainability of your code, especially when dealing with complex data types. For simple data types, such as integers, floating point numbers, or characters, the benefits of using aliases are not obvious. However, for complex data types such as pointers, structures, arrays, and functions, the advantages of using aliases are obvious. A typedef cannot be used before a variable or function definition and is usually created at the top of a program file or after a structure definition.

Linux kernel timers and delay tasks are two commonly used mechanisms to implement scheduled tasks and delayed execution tasks. They allow the driver to execute specific functions at the appropriate time point to adapt to the needs and characteristics of the hardware device. But how do you properly use Linux kernel timers to work with delays? This article will introduce the basic knowledge and skills of Linux kernel timer and delay work driver development from both theoretical and practical aspects, as well as some common problems and solutions. The timer on the kernel timer software ultimately relies on the hardware clock. Simply put, the kernel will detect whether each timer registered to the kernel has expired after the clock interrupt occurs. If it expires, it will call back the corresponding registration function. Do this as an interrupt to the bottom half. Reality

To write a simple firework code in C, you need to follow these steps: Include header files and libraries. Define constants and macros. Create a particle data structure. Declare global variables. Initialize the fireworks particles in the main() function. Update the particle's position and velocity in the game loop and draw them. Check for and destroy particles that have reached their end of life.

The difference between typedef struct and struct: typedef struct creates an alias of a structure type, while struct defines a new structure type. The alias created by typedef struct can be used after it is declared, while the structure defined by struct can be used after it is defined. Neither typedef struct nor struct creates additional storage space.

Function pointer technology can improve code efficiency and reusability, specifically as follows: Improved efficiency: Using function pointers can reduce repeated code and optimize the calling process. Improve reusability: Function pointers allow the use of general functions to process different data, improving program reusability.

I'm trying to create the possibility to call a rust function from go and then said rust function calls back the function to go. I'm using cgo as the ffi interface between go and rust. The following is my go code (src/main.go): packagemainimport("c""fmt""unsafe")/*#cgocflags:-i./../lib#cgoldflags:-l./../bin -lgo_move-wl,-rpath=./bin#include"m
