> -----Original Message-----
> From: Cooke, Mark [mailto:mark.co...@siemens.com]
> Sent: woensdag 8 oktober 2014 17:07
> To: users@subversion.apache.org
> Subject: Where to ask for help compiling svn on windows?
>
> Folks,
>
> Where is the best place to get help compiling subversion (on windows 7)?
Is
> it OK to post to the dev list or should I ask here first?
>
> 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
>
> I built the project files using:
>
> gen-make.py -t vcproj --vsnet-version=2012 --with-httpd=D:\svn\httpd --
> with-openssl=d:\svn\httpd\srclib\openssl --with-serf=d:\svn\serf --with-
> sqlite=d:\svn\sqlite --with-swig=c:\programs\swig --with-zlib=d:\svn\zlib
>
> ...and then tried to build the __ALL_TESTS__ target in (Win32) Release
mode.
>
> For background I have been following a combination of:
> [1] http://blogs.collab.net/subversion/building-subversion-on-windows-a-
> walk-through
> [2] http://httpd.apache.org/docs/current/platform/win_compiling.html
> [3] https://www.apachehaus.net/build/buildapache.html
>
> I have also seen [4] Ben's perl script but I am not familiar enough with
perl to
> understand the script, and the build VM has no internet connection to
> connect to repos etc.
>
> [4] http://svn.haxx.se/dev/archive-2013-04/0332.shtml
>
> Any help appreciated!
>
> ~ Mark C
>
> P.S. I am currently using Strawberry Perl (rather than ActiveState Perl),
is that
> likely to be an issue?
