0
@@ -25,15 +25,109 @@ New bug page on Bugzilla:
0
Clutter is LGPL licensed.
0
+See the INSTALL file. Info on specific Clutter options;
0
+ --enable-debug=[no/minimum/yes]
0
+ Turn on debugging (default=yes):
0
+ yes: All glib asserts, checks and runtime clutter verbose messages.
0
+ minimum: Just glib cast checks and runtime clutter verbose messagaes.
0
+ no: No glib asserts or checks and no runtime clutter verbose messages
0
+ (Only really of use in extreme performance cases)
0
+ --enable-maintainer-flags=[no/yes]
0
+ Use strict compiler flags (default=no)
0
+ use gtk-doc to build API documentation (default=no). Requires gtk-doc
0
+ --enable-manual=[no/yes]
0
+ Build application developers manual. Requires jw and xmlto binaries.
0
+ Assume target hardware has no floating point unit. Useful only
0
+ for embedded targets such as ARM.
0
+ --with-flavour=[glx/eglx/eglnative/sdl]
0
+ Select the Clutter backend: (defualt=glx)
0
+ glx: Fully featured GLX backend. Using Open GL.
0
+ eglx: EGL/Open GL ES backend for EGL on X windows implementations
0
+ eglnative: EGL/Open GL ES backend on 'native windowing system' - i.e
0
+ raw framebuffer. Expects EGL implementation to provide a
0
+ createNativeWindow () call. Also optionally supports
0
+ tslib for touchscreen events.
0
+ sdl: Basic SDL backend, using Open GL. Should provide portability
0
+ to windows and possibly other OS's.
0
+Clutter uses the common "Linux kernel" versioning system, where
0
+even-numbered minor versions are stable and odd-numbered minor
0
+versions are development snapshots.
0
+Different Minor versions break both API and ABI but are paralell
0
+installable. The same Minor version with differing Micro version is
0
+expected to be ABI compatible with other micro versions. Though this
0
+is not guarenteed, especially for odd numbered minor releases, we'll
0
+try our very hardest (promise).
0
+If you want to hack on and improve clutter check the contained TODO
0
+file for pending tasks and HACKING for general coding guidelines.
0
+Bugs should be reported to the OpenedHand Bugzilla at:
0
+ http://bugzilla.o-hand.com/enter_bug.cgi?product=Clutter
0
+You will need an account.
0
+In the report you should include:
0
+* what system you're running Clutter on;
0
+* which version of GLib, GdkPixbuf and OpenGL you are using;
0
+* which video card and which drivers you are using, including output of
0
+* how to reproduce the bug.
0
+If you cannot reproduce the bug with one of the tests that come with Clutter
0
+source code, you should include a small test case displaying the bad
0
+If the bug exposes a crash, the exact text printed out and a stack trace
0
+obtained using gdb are greatly appreciated.
0
+Patches should be submitted using Bugzilla. Patches fixing a bug should be
0
+attached to the bug report; patches for new features or for fixing bugs not
0
+yet reported should be attached to a newly opened bug. Patches should always
0
+be in the unified diff format.
0
Relevant information for developers with existing Clutter applications
0
-wanting to port to newer releases
;0
+wanting to port to newer releases
(See NEWS for general new feature info).0
Release Notes for Clutter 0.3.1
0
-------------------------------
0
@@ -109,35 +203,3 @@ Release Notes for Clutter 0.3
0
ClutterContainer::actor-added and ClutterContainer::actor-removed should
0
-If you want to hack on and improve clutter check the TODO file.
0
-Bugs should be reported to the OpenedHand Bugzilla at:
0
- http://bugzilla.o-hand.com/enter_bug.cgi?product=Clutter
0
-You will need an account.
0
-In the report you should include:
0
-* what system you're running Clutter on;
0
-* which version of GLib, GdkPixbuf and OpenGL you are using;
0
-* which video card and which drivers you are using, including output of
0
-* how to reproduce the bug.
0
-If you cannot reproduce the bug with one of the tests that come with Clutter
0
-source code, you should include a small test case displaying the bad
0
-If the bug exposes a crash, the exact text printed out and a stack trace
0
-obtained using gdb are greatly appreciated.
0
-Patches should be submitted using Bugzilla. Patches fixing a bug should be
0
-attached to the bug report; patches for new features or for fixing bugs not
0
-yet reported should be attached to a newly opened bug. Patches should always
0
-be in the unified diff format.
Comments
No one has commented yet.