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

Re: Using Subversion's API

From: D.J. Heap <djheap_at_gmail.com>
Date: 2006-07-18 14:36:23 CEST

On 7/17/06, Ahmed Reza <ahmedrezat@gmail.com> wrote:
> Hi, I'm need some direction as far as woring with the subversion API goes.
> Can someone please point me in the direction of some already existing
> examples for working with Subversion's API, specifically using Visual C++.
> I know I can look at tortoise, but I'm being lazy, and would really
> appreciate it if someone could point me to a dumbed down step by step
> instruction on how to work with the subversion API, i.e. includes I'm going
> to need, libraries I might need to import etc etc etc, to build an app in
> C++/MFC that uses Subversion. Any input would be really appreciated.
> Regards,
> Ahmed

What version of Visual C++ and what kind of API usage are you looking
at? Client side stuff like manipulating working copies, commiting
changes, etc., or server side direct repository access?

In general, it is the same as any other C/C++ project: Include the
header files for the API's you need and link to the API libraries. If
you want to code against Subversion 1.3.2, then download the
svn-win32-1.3.2_dev.zip, svn-win32-libintl.zip, and
db-4.3.28-win32.zip files that contain the headers and libraries
you'll need (or build them yourself from source).

Add all their include and lib directories to the appropriate places in
your Project Settings, #include the headers you want in your code, add
the libraries (you'll need to add pretty much all of them, probably)
to your linker dependencies and start coding. Look at the source for
minimal_client.c in tools\examples for some basic client API usage.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 18 14:37:46 2006

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.