Build Clutter with profiling instrumentation. Requires the GNU
C Compiler and the UProf library.
- --enable-conform=[yes/no]
- Build the Clutter conformance test suite.
+ --disable-tests
+ Disable building the Clutter tests suite.
+
+ --disable-examples
+ Disable building the Clutter API reference examples.
--enable-deprecated=[yes/no]
Whether deprecated symbols should be available when compiling Clutter.
• what system you're running Clutter on;
• which version of Clutter you are using;
- • which version of GLib and OpenGL (or OpenGL ES) you are using;
+ • which version of GLib, Cogl, and OpenGL (or OpenGL ES) you are using;
• which video card and which drivers you are using, including output of
glxinfo and xdpyinfo (if applicable);
• how to reproduce the bug.
http://git.fishsoup.net/cgit/git-bz/
+Patches submitted against Clutter have to pass the conformance test suite, or,
+if possible, add new unit tests for the conformance test suite in case of new
+features. Ensure you run the conformance test suite every for every patch you
+wish to submit, by using:
+
+ cd tests/conform && make test
+
+and verifying that the test suite passes.
+
RELEASE NOTES
-------------------------------------------------------------------------------
Release Notes for Clutter 1.10
-------------------------------------------------------------------------------
+• The ClutterActor::paint, ClutterActor::queue-redraw, and
+ ClutterActor::queue-relayout signals are now annotated as not allowing
+ signal emission hooks; this enables some optimization inside GLib, and
+ given the amount of emissions these three signals have, we want to get
+ through all the fast paths we can.
+
+• The ClutterActorBox parameter of the ClutterActor::allocation-changed
+ signal is now marked as G_SIGNAL_TYPE_STATIC_SCOPE.
+
+• The clutter-stage-window.h header is not installed any more; this header
+ was never meant to be public in the first place, and nothing could have
+ been implementing the ClutterStageWindow interface and use it with Clutter.
+
+• ClutterActor will call its unmap() implementation when it is removed from
+ its parent. This may happen after the ClutterActor::destroy signal has been
+ emitted, i.e. during its dispose(). Prior to 1.10, calling the
+ clutter_actor_destroy() function would unmap the actor first, and then
+ emit the destroy signal. This means that extra care should be used when
+ overriding the map() and unmap() virtual functions, to avoid dereferencing
+ NULL pointers. It is also worthy of note that since Clutter 1.8, overriding
+ map() or unmap() is not required any more for subclasses of ClutterActor
+ that have children, as ClutterActor will automatically do the right thing
+ inside its own implementation, and map or unmap its children when needed.
+
• ClutterBox and ClutterGroup have been deprecated. ClutterActor should be
used directly, instead. Since ClutterStage inherits from ClutterGroup, the
instance and class structures are still available, but subclassing Group