On Tue Dec 2, 2025 at 8:15 AM CET, Diogo Behrens wrote: > > I think it is not only the name of the procedure that was wrong. But now I > think > I understand the intention of the wrapper. By adding #> int foo(void); #< to > the > wrapper, it compiled and I could run this in csi: > > (import foo-wrap) > (foo) ;; output as expected: 170 > > With that I can probably write the wrappers by hand and try to test my crunch > modules.
Version 0.993 of CRUNCH now includes the generated file, note that an output-filename has to be supplied now when wrappers are generated. This isn't the most elegant solution, but should handle most uses of wrappers (e.g. as CHICKEN extensions or when writing testing modules for CRUCHed code). cheers, felix
