Quoting Mike Pape <[EMAIL PROTECTED]>:
I don't understand why you had to build and install swig? For me this
wasn't necessary at all.
I know nothing about swig so I just assumed it was needed to build and
use swig bindings... I thought it checked for it during the configure.
If it's not necessary, then it shouldn't be included in the new
branch.
Ok, I just wanted to ask because there might have been an important
reason for that.
Just for the record: SWIG is a wrapper generator. It will generate
"glue code" that enables using functions written in language x also
from language y (here: to have libsvn's C functions available also in
perl). It does so by processing the SWIG definitions files "foobar.i"
and generating corresponding C code "foobar.c", which contains plenty
of unreadable but magic code to achieve the wrapper functionality.
Once that "foobar.c" code has been generated, it doesn't need to be
regenerated unless "foobar.i" or any of its included C headers
changed. When the subversion people generate their tarball, they will
include the most up-to-date generated foobar.c files. For us this
means we should never have to regenerate the foobar.c files. This in
turn means we don't need SWIG.
This is one of the major advantages of SWIG over all other wrapper
generators that I know of.
Christian
