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

Re: VC++ 2005 Express build

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-12-16 23:15:23 CET

D.J. Heap wrote:
> On 12/16/05, Stefan Küng <tortoisesvn@gmail.com> wrote:
> [sinp]
>> Isn't that what the apr*_fake projects are for? All Subversion modules
>> depend on those fake projects. But the __ALL__ project depends on the
>> real apr projects too. What I now need is a project which depends on all
>> Subversion projects but *not* the real apr projects.
> They are for setting up library dependencies on other libraries.
> The problem is that the dependencies are a chain...I don't know how to
> create a project (fake or not) that depends on Subversion but doesn't
> depend on apr, when Subversion depends on apr.

Of course, it won't really build if you don't have the apr libs built

> It looks like you can setup a new Build Configuration (like
> ReleaseNoApr) and deselect the apr projects so they don't get
> built...but you still have to build Release first to get apr built, so
> that's not too good.

That's what would help me a lot. As I said, I build Subversion twice
(once complete and once only with working copy features, without any
network modules). So with such a project, I could first build the apr
libs, then build Subversion without any network modules and then build
Subversion completely. And I wouldn't have to build the apr modules
twice too.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 16 23:16:15 2005

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.