[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: swig and bindings for 1.2

From: John Lenz <lenz_at_cs.wisc.edu>
Date: 2005-03-29 08:08:37 CEST

On 03/28/05 04:16:54, Max Bowsher wrote:
> John Lenz wrote:
>> We recently added the -external-runtime option to SWIG so that code like
>> swigutil_py.c does not need to include files directly from a SWIG
>> install.
>> If you use the -export-runtime argument, you won't need that ifdef that
>> is
> Typo? s/export-runtime/external-runtime/ ?

Yes, that is a typo.

>> Secondly, to support building subversion without SWIG installed, you can
>> look for a folder named SWIG or SWIG-version inside the subversion
>> directory, run ./configure && make, and then run SWIG/preinst-swig to
>> generate the wrappers (and run preinst-swig to create the swigpyrun.h
>> file).
> In the interests of keeping the size of our source tarball down, I'd
> rather require that the release manager have swig installed, and just
> include the pregenerated files in the final tarball.

I don't think you understand correctly... SWIG source itself would not be
included in the tarball, just the generated files.

SWIG has always been able to run itself from the build directory without
running make install. This is used for example by our test suite and
such. We recently made it easier to run SWIG directly from the build
directory without having to run make install by adding a preinst-swig.in
script (which gets turned into preinst-swig).

So if you compile SWIG wherever and then run
$ /path/to/SWIG/preinst-swig -options ....
and then you run make install to install SWIG and run
$ swig -options....

These two do exactly the same thing (where the second one searches for swig
on the path and so on) and will produce exactly the same files. And it is
only the generated files that need to be added into the tarball.

You just have to keep in mind that SWIG is now a build time only tool that
exports C and python code that is stand alone and that SWIG can be run to
generate that code directly from the build directory without installing it.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 29 08:29:32 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.