On 7/12/06, Paul Burba <paulb@softlanding.com> wrote:
> I recently set up a dedicated Windows environment for testing RCs. Right
> now I test [ fsfs | bdb ] x [ file | svn | http ] but not any of the
> bindings. I had some time so figured why not be a good citizen and set
> things up to test the Python, Perl, and Ruby bindings too? I don't really
> know much about SWIG, but hey, there are directions at
> subversion/bindings/swig/INSTALL, so it can't be that hard right?
>
> The first three steps in "BUILDING SWIG BINDINGS FOR SVN ON WINDOWS" are
> straightforward, but when I try to build Subversion I have problems with
> all of the swig_*.dsp project files, they seem to be created ok, but msdev
> chokes on them:
>
Yes, it looks like swig on Win32 has been broken relatively recently.
I built and played with the python bindings not too long ago (couple
months I think). But now I get errors with the vcproj build as well:
------ Build started: Project: swig_python_core, Configuration:
Release Win32 ------
Performing Custom Build Step
C:\Apps\swig\Lib\exception.i(11): Error: CPP #error ""This version of
exception.i should not be used"". Use the -cpperraswarn option to
continue swig processing.
Project : error PRJ0019: A tool returned an error code from
"Performing Custom Build Step"
Project : warning PRJ0018 : The following environment variables were not found:
$(top_srcdir)
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 13 05:01:05 2006