git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>, cte <cestreich@gmail.com>,
	git@vger.kernel.org
Subject: Re: linking libgit.a in C++ projects
Date: Sun, 3 Aug 2008 22:12:11 +0200	[thread overview]
Message-ID: <20080803201211.GA11121@steel.home> (raw)
In-Reply-To: <32541b130807311155v50ee6ddaha1bba2f56e9bd61d@mail.gmail.com>

Avery Pennarun, Thu, Jul 31, 2008 20:55:26 +0200:
> On 7/31/08, Alex Riesen <raa.lkml@gmail.com> wrote:
> > Boaz Harrosh, Thu, Jul 31, 2008 15:04:50 +0200:
> > > 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.
> >
> > no, it wont. He still have to resolve name conflicts at the link time.
> 
> Language keywords (as opposed to function names) like 'new' and
> 'typename' are definitely not exported to the object files.  Moreover,
> function parameter names aren't either.
> 

Didn't mean them. Meant the globally visible names. libgit does not
use a prefix for its exported symbols. They will clash with the
symbols of the programs it is linked to.

  reply	other threads:[~2008-08-03 20:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  9:53 linking libgit.a in C++ projects cte
2008-07-31 10:57 ` Dmitry Potapov
2008-07-31 11:10   ` cte
2008-07-31 11:16     ` Pedro Melo
2008-07-31 11:20       ` Petr Baudis
2008-07-31 11:20       ` cte
2008-07-31 18:27     ` Sverre Rabbelier
2008-07-31 21:44       ` cte
2008-07-31 21:51         ` Sverre Rabbelier
2008-07-31 21:58           ` Shawn O. Pearce
2008-07-31 22:10             ` Sverre Rabbelier
2008-08-04 14:52             ` Steve Frécinaux
2008-08-01  1:17           ` cte
2008-08-01  1:54             ` Linus Torvalds
2008-08-01  2:12               ` cte
2008-07-31 22:23         ` Dmitry Potapov
2008-07-31 11:14   ` Petr Baudis
2008-07-31 11:18     ` cte
2008-07-31 12:34     ` Dmitry Potapov
2008-07-31 13:04 ` Boaz Harrosh
2008-07-31 14:44   ` Dmitry Potapov
2008-07-31 18:37   ` Alex Riesen
2008-07-31 18:55     ` Avery Pennarun
2008-08-03 20:12       ` Alex Riesen [this message]
2008-08-04  8:57         ` Boaz Harrosh
2008-07-31 21:31   ` cte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080803201211.GA11121@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=bharrosh@panasas.com \
    --cc=cestreich@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).