I think i found the majority of my problems. Seems as though its
building in VC2012 at the moment. For libintl the path you specify the
gen-win.py looks for path/inc and path/lib. For the headers and lib
where as GnuWin32 installs include and lib. Then bdb it looks for
path/lib/libdb$version
These feel too hard to find or at least should be documented since there
is very little to no standardization on windows development libraries.
Why not have dependancy-include-dir and dependancy-lib-dir for each for
each of them? Although your gen-make.py is going to be huge but at least
its a little more simple to see whats pointing to where.
Then what happens with ruby and perl bindings for their respective lib
and include paths. And now i just noticed my libintl lib must be wrong
since its looking for intl3_svn.lib and now its failing because i didn't
specify a junit.
--Phil
On 05/10/12 16:17, Philip Herron wrote:
On 05/10/12 16:14, Bert Huijben wrote:
-----Original Message-----
From: Mark Phippard [mailto:markp...@gmail.com]
Sent: vrijdag 5 oktober 2012 17:00
To: Philip Herron
Cc: dev@subversion.apache.org
Subject: Re: 1.7.7 up for testing/signing
On Fri, Oct 5, 2012 at 10:51 AM, Philip Herron
<philip.her...@wandisco.com> wrote:
Decided to try using the 2010 vcnet version for gen-make.py, and
upgraded
in
VC2012. But running msbuild subversion_bla.sln /p:UseEnv=true fails
miserably. Running in VC looks like its working. But i need to tell it
to
include and lib paths Which seems painful.
I do my Windows builds using command line. I believe I am currently
using VS 2008 for the builds I sign. When you install VS, it installs
a shortcut that opens a Windows command prompt with all of the VS
envvars already set. That is what I use as my starting point. I then
just have some batch files that run the Python script and follow that
by running the "devenv" command to build the solution. This is pretty
much how I have always done it going back to MSVC 6. The only thing
that really changed was the name of the command line tool to build the
solution.
Bert also has build scripts that he uses that use MSBuild. I know
these work with VS 2010, but not sure if he updated them yet for 2012.
The 2012 specific support hasn't been merged to 1.7.x (yet), but
opening the
2010 project in Visual Studio 2010 allows you to upgrade them to 2012
with a
few mouseclicks.
(I don't use the UseEnv flag)
Bert
Hey
Thanks yeah i did the upgrade to 2012 thing. But i dont know how you
dont use UseEnv since i get errors of no libintl.h. Maybe i need to
point to a different location?
--Phil
