| valabind(1) | 1 (valabind manual page) | valabind(1) |
NAME
valabind — vala to
swig interface conversor
SYNOPSIS
valabind |
[-h] [-x]
[-v] [-V
vapidir] [-o
ofile] [-m
modname] [-p
profile] [-N
namespace] [-D
SYMBOL] [--swig]
[--node-ffi] [--ctypes]
[--gir] [--cxx]
vapifile |
DESCRIPTION
Valabind is a program written in Vala that aims to generate nodejs, c++ or SWIG interfaces (.i) from a vala-generated or hand-made vapi files.
SWIG opens the door to create bindings for Python, Perl, ruby, lua, and many other scripting languages.
-h- show help message
-oOUTPUT- specify output file name
-mNAME- specify module name
-NNS- include given namespace for processing
-DSYMBOL- define a preprocessor symbol inside Vala code
-pPROFILE- select Vala profile (posix, gobject, dova)
-x- generate c++ code for SWIG bindings
-v- show version information
-VPATH- specify an alternative vapidir path
NOTES
Valabind processes a single module at a time: the module named
with -m is the only one whose classes, structs,
enums and methods are emitted in the output. Any additional
vapifile arguments passed on the command line are not
processed as independent modules — only the first class of the first
file ends up being walked.
To resolve types that come from other modules (e.g. a
r_core.vapi that references symbols declared in
r_asm.vapi), drop the extra vapis and their sibling
.deps files under the directory passed to
-V VAPIDIR and invoke valabind
with just the single positional vapi you want emitted. Reproducing the
pipeline by hand with every .vapi on the command
line is a common mistake and will silently produce a nearly empty
binding.
ENVIRONMENT
- XDG_DATA_DIRS
- Standard freedesktop environment variable to point to the share prefix directory where vala looks for vapi files.
HYPER-REFERENCES
SEE ALSO
AUTHORS
pancake <pancake@nopcode.org>
Eduard Burtescu <edy.burt@gmail.com>
| November 15, 2012 | radare |