On Jul 31, 2008, at 12:10 PM, cte wrote:
On Thu, Jul 31, 2008 at 3:57 AM, Dmitry Potapov <dpotapov@xxxxxxxxx>
wrote:
On Thu, Jul 31, 2008 at 02:53:37AM -0700, cte wrote:
However, the git source uses a few reserved C++ keywords; namely
'typename', and 'new'.
Because this source code are meant to be compiled by C and not by C+
+!
Even if we will have real git library for other applications to use,
it still be compiled only by C. Thus, C++ keywords are not issue.
[...]
Fortunately, g++ can compile C programs and link static libraries that
were compiled by C compilers, unless of course, they use C++ keywords.
I don't think it is unreasonable to rename the _very few_ C++ keywords
in git's source in the interest of allowing C++ projects to leverage
libgit.
I think the point Dmitry was trying to make is that you should compile
libgit as C, using gcc, and then link it with your C++/Objective C code.
No patch is required to git, only to your makefile/xcode project file.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: melo@xxxxxxxxxxxxxxxx
Use XMPP!
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
