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

Re: compile failure and other trouble

From: Cynic <cynic_at_mail.cz>
Date: 2001-08-13 10:44:02 CEST

At 00:40 8/12/2001, Branko =?ISO-8859-2?Q?=C8ibej?= wrote the following:
--------------------------------------------------------------
>Cynic wrote:
>
>>3)
>>
>>It's not really necessary to require people to define $(SVN_DB3_WIN32):
>>all that you need is put the include/ and lib/ directories in the appropriate
>>lists in Tools -> Options -> Directories in MSVC, and you can get rid of those
>>/I $(SVN_DB3_WIN32)/include and just "ADD LINK32 libdb32.lib" in the .dsp files.
>>
>>I can send the patches since I've already done this -- didn't like the idea I had
>>to restart my computer just to compile Subversion.
>
>Why would you have to restart the ... Ah, Win9x, and autoexec.bat, and similar horrible things. Yep, I wasn't really thinking about those windosaurs when I wrote the original .dsps.

Well, I'll welcome if you prove me wrong, but I use NT 4 and 5, and both require
restart for env. vars created through the control panel to become effective.

>O.K., I don't mind if we change this. If you've got the patches ready, great, just post them here, thanks!

Will do so later today.

>Oh, one little detail: could you also prepare a patch for HACKING, describing the new way of building things on Windows? Just so that people will know they have to modify the library paths in MSDev.

Sure.

cynic@mail.cz
-------------
And the eyes of them both were opened and they saw that their files
were world readable and writable, so they chmoded 600 their files.
    - Book of Installation chapt 3 sec 7

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:35 2006

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.