John Lenz wrote:
I have recently been working on the guile module (as discussed before....) and to help test it I have added a bunch of _runme.scm files to the guile test-suite. Mostly I just copied the python tests. What I mean is the guile tests call exactly the same functions as the _runme.py files. Also a couple of tests (name_runme.scm, list_vector_runme.scm, and char_constant_runme.scm) were not calling the correct initilization function, so I fixed those too. git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@4193 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
83e0c52c5a
commit
e3eb2528cb
13 changed files with 175 additions and 3 deletions
|
|
@ -1,7 +1,7 @@
|
|||
;; The SWIG modules have "passive" Linkage, i.e., they don't generate
|
||||
;; Guile modules (namespaces) but simply put all the bindings into the
|
||||
;; current module. That's enough for such a simple test.
|
||||
(dynamic-call "scm_init_test_module" (dynamic-link "./libname.so"))
|
||||
(dynamic-call "scm_init_name_module" (dynamic-link "./libname.so"))
|
||||
|
||||
(foo-2)
|
||||
bar-2
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue