On 03/31/05 05:08:24, Max Bowsher wrote:
> John Lenz wrote:
>> On 03/28/05 04:16:54, Max Bowsher wrote:
>>> John Lenz wrote:
>>>> Secondly, to support building subversion without SWIG installed, you
>>>> 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
>>> 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.
> Oh, I do understand that.
> I'm just saying that the release manager and developers should probably
> just install SWIG normally, rather than teaching Subversion to build
> SWIG, and rebuilding it every time it is needed.
And if you don't want to limit support to only 1.3.25 (I see the 1.2
release process is starting, I thought it was a little further away), you
can do something like this in the makefile. I would say 1.2 should support
1.3.24 and above, with something like the following in the Makefile
$(SWIG) -python -external-runtime path/swigpyrun.h || \
( cat $(SWIGLIBDIR)/swigrun.swg > path/swigpyrun.h && \
cat $(SWIGLIBDIR)/python/pyrun.swg >> path/swigpyrun.h && \
cat $(SWIGLIBDIR)/runtime.swg >> path/swigpyrun.h; )
and then have the swigutil_py.c file include swigpyrun.h and have
the make dist depend on swigpyrun.h and all the _wrap.cxx files. Then you
just need to include swigpyrun.h and all the _wrap.cxx files in the
tarball. Notice then you don't need to have the swiglabels.swg file, since
the cats will only run with 1.3.24.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Mar 31 23:51:59 2005