Paul Burba <email@example.com> wrote on 07/26/2006 09:42:01 AM:
> "D.J. Heap" <firstname.lastname@example.org> wrote on 07/24/2006 04:44:16 PM:
> > On 7/24/06, Paul Burba <email@example.com> wrote:
> > [snip]
> > >
> > > Thanks for taking a look, unfortunately the problems you found with
> > > $(top_srcdir), #error, and #warning appear unrelated to my swig
> > > difficulties. I tried 1.3.25, but building with VC++6.0 gives the
> > > errors:
> > >
> > > Found installed SWIG version 1.3.25
> > > Using SWIG library directory C:\SVN\SWIG\Lib
> > > Found ML, ZLib build will use ASM sources
> > > Found neon version 0.25.5
> > > Configuring apr-util library...
> > > perl "..\httpd-2.0.58\srclib\apr-util\build\w32locatedb.pl" dll
> > > "db4-win32\include" "db4-win32\lib"
> > > Using BDB version 4.4.20
> > [snip]
> > > The file
> > > has been modified and cannot be loaded as a Developer Studio
> > > The file C:\SVN\src-trunk\build\win32\msvc-dsp\swig_ruby_wc_msvc.dsp
> > > been modified and cannot be loaded as a Developer Studio project.
> > >
> > > I've googled, altavistaed, lycosed, and otherwise yahooed this error
> > > message to within an inch of its life and haven't found anything
> > > except some vague discussion of dsp file corruption due to line
> > > problems.
> > >
> > > I don't imagine this matters, but I'm running these tests on a
> > > virtual machine. I remain completely baffled at the moment but will
> > > continue to look into this.
> > Very strange -- I'm running everything under VMWare Workstation 5.5.1,
> > by the way, so that doesn't seem likely to be the problem. I'm using
> > VS6 with Service Pack 6 with the latest Platform SDK and not seeing
> > any problems aside from the top_srcdir warning anymore.
> > Actually, I did have to tweak a Python header to comment out a line
> > that was defining socklen_t or something like that -- the lastest
> > Platform SDK typedef's it which was conflicting with Python's #define.
> > Anyway, if you figure out anything else please share.
> A quick update:
> Building 1.4.x r20780 (i.e. RC4) on my regular (non-virtual) machine and
> using swig 1.3.25, I was able to build the Python bindings with only the
> top_srcdir warning. So now it's a *simple* matter of figuring out how
> VM and regular machines differ :-P I'm putting this aside for a while,
> but when I eventually track down the problem I'll post an explanation.
While testing the 1.4.1 zips the other day I was reminded of this problem:
"C:\SVN\src-trunk\build\win32\msvc-dsp\swig_*_msvc.dsp has been modified
and cannot be loaded as a Developer Studio project."
I glanced back at this thread, and there it was, staring me in the face,
you said: "I'm using VS6 with Service Pack 6"...
My regular machine had SP6 installed, but sure enough my virtual machine
didn't -- I wish MS made it simpler to know what MSVC SP is installed, but
that's another story...
Anyway, I installed SP6 and the above problem disappeared.
May someone someday have the same problem, find this thread, and rejoice
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 1 18:26:48 2006