[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Building on Windows

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-05-10 03:01:53 CEST

D.J. Heap wrote:

> I have a patch for the dsp template that adds resources back into
> exe's and Apache modules, and moves the output back into the
> sourcetree which I think is where it should go for the tests...but
> that means all the exe's (tests as well as svn.exe, etc) are in the
> source directories, and I'm not sure if that's desired...?

No, the programs shouldn't go into the source tree; but the output tree
should have the same structure as the source tree. So, for example,
svn.exe should go into ./Release/subversion/clients/cmdline/svn.exe

> A couple of problems I've noticed are that SVN_FILE_NAME which is used
> for the Original File Name version property is not set anywhere,

You have to define that in the .dsp. The sections in build.conf should
get a new parameter that gets defined as "SVN_FILE_NAME".

> I also am still having problems building most of the tests due to the
> link error: "LINK : fatal error LNK1561: entry point must be defined",
> but I'm starting to think maybe that is just a conversion problem
> since no one else seems to be having trouble...

No, it's not a conversion problem. It happens to me, using VC6, too.

> It appears that the conversion process just *drops* any source files
> that do not exist from the project. IE, getdate.c which is generated
> for libsvn_subr gets dropped from all projects that reference it

My original patch copied getdate.c and svn_private_config.h to the right
places before generating the .dsp's. I dunno if Greg committed that part
or not.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 10 03:04:54 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.