RE: Where to ask for help compiling svn on windows?

> -----Original Message-----
> From: Cooke, Mark [mailto:mark.cooke_at_siemens.com]
> Sent: donderdag 9 oktober 2014 10:47
> To: users_at_subversion.apache.org
> Cc: Bert Huijben
> Subject: RE: Where to ask for help compiling svn on windows?
>
> > -----Original Message-----
> > From: Bert Huijben [mailto:bert_at_qqmail.nl]
> > Sent: 08 October 2014 17:18
> >
> > > -----Original Message-----
> > > From: Cooke, Mark [mailto:mark.cooke_at_siemens.com]
> > > Sent: woensdag 8 oktober 2014 17:07
> > > To: users_at_subversion.apache.org
> > > Subject: Where to ask for help compiling svn on windows?
> > >
> > > Specifically, I am trying to build subversion on windows 7 using
Visual
> > > Studio 2012. I have got so far (I think I have httpd building OK with
> > > OpenSSL for example, I can run up httpd and connect to the server),
but
> > > the libsvn_client_dll project is failing with:
> > >
> > > LNK1181: cannot open input file
> > > 'D:\svn\src\Release\subversion\libsvn_ra\libsvn_ra-1.lib'
> > >
> > > When I check for libsvn_ra-1.lib I can only find
> > > `d:\svn\src\release\subversion\libsvn_ra\svn_ra-1.lib` so it looks
like
> > > the project files are wrong or I am missing something.
> >
> > If you are building with shared libraries (=without passing
--disable-shared
> > to gen-make.py), you should have both libraries.
> >
> > Most likely this error is caused by an earlier linkage error.
> >
> > Bert
>
> Thanks for the feedback, I was getting quite frazzled after two days
slowly
> assembling a build machine. I went back and did a full __ALL_TESTS__
build
> and got lots of errors, however sorting them gives me multiple instance of
> just the following:
>
> LNK1181: cannot open input file 'serf-1.lib'
> LNK1181: cannot open input file
> 'D:\svn\src\Release\subversion\libsvn_ra\libsvn_ra-1.lib`
> LNK1181: cannot open input file
> 'D:\svn\src\Release\subversion\libsvn_client\libsvn_client-1.lib'
> LNK1181: cannot open input file
> 'D:\svn\src\Release\subversion\bindings\swig\python\libsvn_swig_py\libsv
> n_swig_py-1.lib'
>
> ...plus...
>
> C1083: Cannot open include file: 'stdbool.h': No such file or directory
> c:\strawberry\perl\lib\core\handy.h 77
> C1083: Cannot open include file: 'ruby.h': No such file or directory
> D:\svn\src\subversion\bindings\swig\ruby\svn_wc.c 821
>
> ....which I assume come from the perl or ruby bindings (I need neither).
>
> So it looks like I need to start with serf ~ did this used to be part of
the
> subversion build? [1] does not mention any build steps for serf so I
assumed
> it was built by svn. Checking the solution it looks not to be the case,
though,
> so I investigated further and find:

We used to build serf from Subversion, but this is no longer possible after
Serf switched to a new buildsystem. We now require building serf separately,
before Subversion.

Do you have a patch for the documentation?

>
> http://mail-archives.apache.org/mod_mbox/subversion-
> dev/201308.mbox/%3C00fc01ce9fe4$1c2bde80$54839b80$@qqmail.nl%3E
>
> ...so I now have serf and subversion built (Rebuild All: 89 succeeded, 0
failed,
> 0 skipped; running tests now).
>
> However, I am also seeing a _lot_ of warnings similar to:
>
> RC4011: identifier truncated to '_CRT_USE_WINAPI_FAMILY_DESKTOP_'
> C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\string.h
>
> ...can you help with those? The search results I have so far were not
very
> enlightening.

These warnings started a few VS versions back...
This is caused by unnecessary inclusion of quite a few windows headers in
the .rc file. (We only include a subset on trunk, which will eventually
become 1.9).
You can safely ignore the RC* errors if the build continues successful.

They are only interesting for the generation of the win32 resources inside
our DLLs. Not something a typical user cares about.

For the swig bindings I would recommend only building the ones that you care
about... They are not that well maintained on Windows. (We ignore quite a
few errors on our buildbots).

Patches welcome if you find out how to fix the problems though, :-)

(My involvement in the Subversion project started exactly in the same way as
you work your way into it now...)

        Bert
>
> ~ mark c
Received on 2014-10-09 16:46:49 CEST