On Apr 12, 2005 1:33 PM, John Lenz <email@example.com> wrote:
> 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.
> 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.
Well, I managed to get a little bit more progress by moving around a
bunch of the .h files. But apr.h seems to be missing. I saw apr.h.in
and that seems to be what I'm looking for. It says apr.h is a
generated file? How do I generate it? On a whim, I tried just
renaming apr.h.in to apr.h and got back an error from SWIG:
E:\svn-source\subversion-1.1.4\subversion\bindings\swig>swig -ruby apr.i
apr.h(257): Error: Syntax error in input.
*** No module name specified using %module or -module.
So I assume that was the wrong thing to do :-P
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Apr 12 20:13:13 2005