sugarlabs/sugar-toolkit-gtk3
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
80c6028ddd
sugar-toolkit-gtk3/Makefile.am

15 lines
284 B
Makefile
Raw Normal View History

Fix regeneration of ./configure from configure.ac when using make To use an m4 macro library you need three things: * configure.ac mentions it (OK) * autogen.sh mentions it (OK) * Makefile.am mentions it (fixed by this patch) Omission of the third part means that when you change configure.ac and run make, ./configure is rebuilt without using the m4 directory, so autoconf doesn't load python.m4 and the rebuild fails.
2007-08-07 14:13:23 +02:00
ACLOCAL_AMFLAGS = -I m4
Switch sugarext to be an introspectable library This makes sugarext accessible through introspection. It is used from the shell (key grabber, sound volume management) and the shell session management. Making the sugarext introspectable was done following the descriptions at: http://live.gnome.org/GObjectIntrospection#Using_GI Signed-off-by: Simon Schampijer <simon@schampijer.de>
2011-11-13 17:03:44 +01:00
DISTCHECK_CONFIGURE_FLAGS = --enable-introspection
Fix regeneration of ./configure from configure.ac when using make To use an m4 macro library you need three things: * configure.ac mentions it (OK) * autogen.sh mentions it (OK) * Makefile.am mentions it (fixed by this patch) Omission of the third part means that when you change configure.ac and run make, ./configure is rebuilt without using the m4 directory, so autoconf doesn't load python.m4 and the rebuild fails.
2007-08-07 14:13:23 +02:00
Make it distcheck. Fix license.
2008-02-06 16:43:10 +01:00
DISTCLEANFILES = \
intltool-extract \
intltool-merge \
intltool-update
EXTRA_DIST = \
intltool-merge.in \
intltool-update.in \
intltool-extract.in
sugar-activity: import and make independent of sugar-toolkit GTK versions As we move to adding support for a second UI toolkit (GTK+ 3.x), the sugar-activity binary used by all activities must become backend-toolkit-independent. It would be wasteful to have two backend toolkits loaded in memory, and in the GTK2/GTK3 case, it is impossible (importing both results in an instant crash). To achieve this, we split the existing sugar-toolkit activity/main.py:main() functionality into two parts, moving it into the sugar-activity binary and the Activity class as follows: 1. All toolkit-specific stuff is moved into the Activity class (i.e. everything that interacts with GTK) 2. Everything that can be reasonably/easily moved into the Activity class is also moved. 3. What remains is the stuff that is inherently involved with the construction of the Activity object, not related to UI toolkits. This is moved into the sugar-activity binary. main.py is then removed from sugar-toolkit, and sugar-activity is moved from sugar to sugar-toolkit-gtk3 in order to keep toolkit-related code with the toolkit itself. With this work done, the one remaining question is how to invoke the main loop. An optional run_main_loop() method is added to the activity class, for GTK2 this will run the GTK2 main loop, for GTK3 the GTK3 main loop will be run, etc. Signed-off-by: Daniel Drake <dsd@laptop.org>
2011-12-13 20:47:33 +01:00
SUBDIRS = bin src po
Reference in New Issue Copy Permalink