On 8/6/05, John Lenz <email@example.com> wrote:
> > Perhaps it would be a good idea for us to run SWIG when users type
> > "autogen.sh"? (The SWIG bindings code would only be generated if SWIG
> > 1.3.25 is installed). We already include the generated output of
> > "autogen.sh" in the release tarballs.
> and the other messages on those threads
> and the older rather long thread
> Some of those threads even have patches I wrote... probably don't work
> anymore but it is something you can look at.
> I don't presume to speek for the developers, but the last time this came
> up they seemed to like the idea... but didn't want to do anything prior to
> the release.
> Just to restate: all the files generated from SWIG 1.3.25 can be included
> directly and compiled anywhere... they have absolutly no SWIG
> dependencies. If other code needs access to the runtime type system (like
> subversion), you just need to run SWIG to generate the header file, and
> then that header file is also stand-alone. For more information, you can
> read the Modules chapter
> basicly, just run
> swig -python -external-runtime <filename>
> which I think subversion is already doing... it just isn't doing it before
> the build process.
Thanks for your help, John! I've updated the
python-bindings-improvements branch in r15620 to follow your suggested
process. ./autogen.sh now compiles all SWIG files into standalone C
files if you run it with the --release flag. Users of the bindings
won't need to have SWIG installed, if they download a release version
P.S. The python-bindings-improvements branch now requires SWIG 1.3.24.
David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Aug 8 07:09:10 2005