From: cte <cestreich@gmail.com>
Date: Thu, 31 Jul 2008 21:31:44 GMT
Subject: Re: linking libgit.a in C++ projects
Message-ID: <ac9f0f090807311431p3e943441xce8f2ac03ba1700@mail.gmail.com>
In-Reply-To: <4891B872.3040707@panasas.com>

Excellent idea; thank you!

> The practice of avoiding C++ keywords from public C headers is
> very welcome. You should send a patch and try to push it.
>
> That said the problem can be easily avoided.
>
> Produce a C file and header that defines some stable API to your
> GUI application, that does not expose any git internal headers.
> Then compile that, say git_api.c, with C compiler in Makefile
> and extern "C" link that file to your C++ application. This will
> completely insulate you from any git code.
>
> This could also solve the other problem of API changing, only
> the git_api.c need change, your outer GUI code stays the same.
>
> And if you do all that maybe you can submit it for inclusion
> as a: somewhat stable high-level library, for developers.
> Ala git-dev
>
> Cheers
> Boaz
>
>