After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 575136 - Wrap Gst::Object with gmmproc instead of handwriting source files
Wrap Gst::Object with gmmproc instead of handwriting source files
Status: RESOLVED FIXED
Product: gstreamermm
Classification: Bindings
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on: 574861
Blocks:
 
 
Reported: 2009-03-12 19:52 UTC by José Alburquerque
Modified: 2011-01-16 23:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to have gmmproc wrap Gst::Object (35.79 KB, patch)
2009-03-12 19:53 UTC, José Alburquerque 		none Details | Review
Remove source duplication in object.{hg, ccg} (28.97 KB, patch)
2009-03-12 19:59 UTC, José Alburquerque 		committed Details | Review

Description José Alburquerque 2009-03-12 19:52:49 UTC 
Gst::Object should be wrapped with gmmproc so that when signals and virtual functions are done they can be wrapped and not handwritten.  Migration patch follows.
Comment 1 José Alburquerque 2009-03-12 19:53:49 UTC 
Created attachment 130549 [details] [review]
Patch to have gmmproc wrap Gst::Object
Comment 2 José Alburquerque 2009-03-12 19:59:58 UTC 
Created attachment 130550 [details] [review]
Remove source duplication in object.{hg, ccg}
Comment 3 Murray Cumming 2009-03-13 08:13:22 UTC 
Is this patch here because you need someone to review it?
Comment 4 José Alburquerque 2009-03-13 15:35:17 UTC 
The reason I posted it is so that we don't forget that in order for this to be checked in, the patch in bug #574861 should be resolved.  Without the patch custom code in the constructors (for the floating reference) can't be added.  Also, because this patch uses the macros in the patch of the afore mentioned bug, the compilation would fail without it.  Should I check the patch in bug #574861 in?