Please use git.gnome.org. Feel free to create a branch of glibmm or
gtkmm or whatever if it helps.
Murray
On Thu, 2014-10-02 at 18:21 +0200, Marcin Kolny wrote:
> One more question (for maintainers, I think); should I keep my code on
> a git.gnome.org server in separated branch or somewhere else
One more question (for maintainers, I think); should I keep my code on a
git.gnome.org server in separated branch or somewhere else, e.g. on my
github?
2014-10-01 10:50 GMT+02:00 Marcin Kolny :
> Hi guys,
> Thanks for your reply. Of course, I know that we cannot use typelibs, and
> actually I ju
Hi guys,
Thanks for your reply. Of course, I know that we cannot use typelibs, and
actually I just wanted, as a first step, parse gir files and generate .defs.
gmmproc-refactor branch will be very useful for me, but I'm afraid, that I
can't just continue this branch because of lot of changes meanw
I wasn't aware of that branch. We should start from there, or borrow some
code. Thank you!
Best regards,
Juan.
On Wed, Oct 1, 2014 at 10:16 AM, Kjell Ahlstedt wrote:
> Have you seen glibmm's gmmproc-refactor branch in the git repository (
> https://git.gnome.org/browse/glibmm/?h=gmmproc-refact
Have you seen glibmm's gmmproc-refactor branch in the git repository
(https://git.gnome.org/browse/glibmm/?h=gmmproc-refactor)? Krzesimir
Nowak has started a complete rewrite of gmmproc, using
gobject-introspection, I think. Nothing has been added to that branch
since July 2012. Still, it might
Hi,
I did try to generate C++ bindings for gobject-introspected libraries.
However, all I achieved before losing interest was a gir parser written in
python (you can see advertisement of this in the list's archives).
I don't understand what you mean by 'why don't we use it in mm projects
instead
