[cvsnt] Compiling CVSNT, just which Platform SDK is required?
webpages at sprow.co.uk
Fri Sep 12 09:46:02 BST 2008
On 28 Aug, Arthur Barrett <arthur.barrett at march-hare.com> wrote:
> > I've been trying to compile CVSNT on Windows and seem to be
> > flip flopping
> > between a handful of errors (that appear to be Platform SDK
> > related) and over 100 errors (when changing to a newer Platform SDK).
> Please look at the posts on cvsnt-dev, and if you are still stuck then
> post your questions there.
> For 2.5.03 you need VS.NET 2003 and an SDK that includes XP.
Thanks for pointing out the distinction between cvsnt and cvsnt-dev, Google
dropped me straight into this list when I searched for CVSNT mailing list.
Anyway, I found a similar query in the cvsnt-dev archive and did some more
fiddling round and have now got it to compile plus made my one line change
and it's all working fine thanks!
For the archive (and to finish this thread) here were the important steps:
- Check out tag CVSNT_2_5_03_2382 of cvsnt
- Check out cvsdeps module
- Put both of these on a path with no spaces.
- Install the Microsoft Platform SDK for Windows Server 2003 R2.
- Add a system variable CVSNTDEPS and PLATFORMSDK in "My Computer"
pointing to the respective directories, the path PLATFORMSDK can
include spaces if required.
- Follow the instructions in "CompileOnWindows.txt" for adding the paths to
the project include and library directories (be sure of the Platform
SDK's priority at the top).
- Rename "cvslock.vcproj" to "lockservice.vcproj"
- Open the solution & rebuild all.
- Note you'll get a residual MkManifest error at the end, ignore this,
it doesn't stop the rest of the project form compiling.
More information about the cvsnt