* You set the variable 'VSVERSION' to 2003 if _VC2005 isn't defined. But
> your _VC2005 gets set if VC-Express is used. And I'm building TSVN here
> with VS.NET2005, so the '2003' is wrong and misleading to someone who
> tries to understand the build script.
I'll take that into account, the VS80COMNTOOLS env variable you mentioned,
looks indeed like a better solution.
* You're patching the Subversion build generator to output vcproj files
> for VC2005. You should send that patch to the Subversion mailing list!
> If you're fast enough, they might even get it into the 1.3 release (I
> have my doubts about that though).
Ok, but that patch would need some additional changes. As it is now, it
unconditionally generates VC2005 files, it would still need to be able to
generate "old style" project files for backward compatibility. I'll try to
* You don't patch the Nant build scripts
I don't know which files are the Nant build scripts.... I obviously missed
Can you explain?
* In build.txt you add the requirement of downloading masm - but that's
> only necessary if you're using VC2005, it is installed automatically
> with VS.NET2005 (so no need to download that). You should rearrange that
> requirement to the VC2005 section.
I'll change that.
I don't understand why building an individual project should fail but
> will work as part of a group. Or are you talking about Subversion
> modules? Most of them can't be compiled directly from the IDE because
> you need to pass /useenv (and set the path to the intl module) to make
> it work.
Building SubWCRev alone failed. msbuild complained something about
"SubWCRev" target not present in .sln file. See if it can be fixed.
Received on Thu Dec 15 18:58:40 2005