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

Re: Accessing SVN through Ruby

From: John Lenz <lenz_at_cs.wisc.edu>
Date: 2005-04-12 19:33:56 CEST

On 04/12/05 11:49:17, Bob Aman wrote:
> Ok, so I'm still trying to get SWIG to do its thing on Windows. And
> I'm starting to get the impression that perhaps it's not necessary to
> go through a full build. (At least, I certainly hope so.) Am I
> correct in this assumption, and if so, what is the bare minimum
> necessary to get SWIG to do its magic in Windows? I'm currently
> working with the source for 1.1.4, not the latest code from the
> repository.

http://www.swig.org/Doc1.3/Windows.html

I should also note here that as I have said before, the output files from
SWIG are portable to almost any architecture and only need to be generated
once. Thus, if you have SWIG installed say on linux, you can run it to
generate the _wrap files and those exact wrap files can be used on Sun,
Windows, Linux, MacOS, whatever. So you could even get someone to email
you the files that SWIG creates, and you wouldn't even need SWIG installed
to compile the bindings on windows.

The right way to take care of this problem is to have the SWIG generated
files present directly inside the released subversion tarballs, then SWIG
does not need to be installed to build a tarball. Sadly, this feature will
not even be in the 1.2 release, but hopefully future releases will have it.

Note that all I've said is only true for SWIG since version 1.3.23... but
subversion is using 1.3.24 so shouldn't matter.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 12 19:37:37 2005

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