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

Re: Use of svn-win32-1.5.1_dev.zip

From: D.J. Heap <djheap_at_gmail.com>
Date: Thu, 28 Aug 2008 06:51:13 -0600

On Thu, Aug 28, 2008 at 6:31 AM, D.J. Heap <djheap_at_gmail.com> wrote:
> On Wed, Aug 27, 2008 at 7:06 PM, Tony Butt <tjb_at_cea.com.au> wrote:
>> Dear svn users,
>>
>> I am trying to rebuild an application we have which uses the subversion
>> development libraries.
>>
>> My build tool is Visual Studio 2003.NET on Windows XP, and I can build
>> the application against the svn 1.3.2 development libaries, and the
>> 1.4.3 development libraries, and run it successfully.
>>
>> I can build against the current 1.5.1 libraries (after changing 1 option
>> - now don't exclude LIBCD), but whenever I try to run it, I get an
>> access violation on calling svn_cmdline_init().
> [snip]
>
>
> The problem is stderr -- it is a FILE* which is a CRT type which means
> you have to be using the same CRT as the dll's were built with.
> Unfortunately, there are a few API's where raw CRT types crept in that
> aren't wrapped by APR.
>
> You can either avoid those API's, rebuild Subversion with your
> compiler, or link to the static libraries instead of the dynamic
> libraries and use the no-default-libs option to make sure that your
> CRT is linked in instead of the VC6 one (I believe this is how it
> worked prior to 1.5).

By the way, you can also pass NULL instead of stderr and get past this
particular API call, although, of course, you'll lose any error
message that may have been written to stderr if the call fails.

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-28 14:51:47 CEST

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

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