1 <?xml version="1.0" standalone="no"?> <!--*- mode: xml -*-->
5 <!-- Where to pick up the GTK+ installation, icon themes,
6 etc. Note that "${env:JHBUILD_PREFIX}" is evaluated to the
7 value of the environment variable JHBUILD_PREFIX. You can
8 define additional prefixes and refer to them in paths
9 throughout this file on the form "${prefix:name}". This is
10 useful for installing certain libraries or even the
11 application itself separately. Note that JHBUILD_PREFIX is
12 defined by jhbuild, so it you are not using jhbuild you can
13 either define your own or just hardcode the path here.
15 <prefix name="default">${env:JHBUILD_PREFIX}</prefix>
17 <!-- The project directory is the default location of the created
18 app. If you leave out the path, the current directory is
19 used. Note the usage of an environment variable here again.
21 <destination overwrite="yes">${env:HOME}/projects/chimara</destination>
24 <!-- Not implemented yet (DMG image). -->
27 <!-- Comment this out to keep the install names in binaries -->
28 <run-install-name-tool/>
30 <!-- Optionally specify a launcher script to use. If the
31 application sets up everything needed itself, like
32 environment variable, linker paths, etc, a launcher script is
33 not needed. If the source path is left out, the default
36 <launcher-script>${project}/launcher.sh</launcher-script >
38 <!-- Not implemented: Optional runtime, could be python or mono
41 <!-- runtime copy="yes">/usr/bin/python</runtime -->
42 <!-- Indicate the active gtk version to use. This is needed only
43 for gtk+-3.0 projects. -->
47 <!-- The special macro "${project}" refers to the directory where
48 this bundle file is located. The application name and bundle
49 identifier are taken from the plist file.
51 <plist>${project}/Info-chimara.plist</plist>
53 <main-binary>${prefix}/bin/chimara</main-binary>
55 <!-- Copy in GTK+ modules. Note the ${gtkdir} macro, which expands
56 to the correct library subdirectory for the specified gtk
60 ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/immodules/*.so
64 ${prefix}/lib/chimara/*.so
67 <!-- Copy in GTK+ theme engines and print backends. Note the use of the
68 "${pkg:module:variable}" macro, which evaluates to a pkg-config
69 variable in the specified module. Note that any libraries that
70 binaries link to are also copied in automatically. Note also
71 the included ${gtk} macro, which gets the correct package name
75 ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/engines/*.so
79 ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/printbackends/*.so
82 <!-- Starting with 2.24, gdk-pixbuf installs into its own directory. -->
84 ${prefix}/lib/gdk-pixbuf-2.0/${pkg:gdk-pixbuf-2.0:gdk_pixbuf_binary_version}/loaders/*.so
87 <!-- Translation filenames, one for each program or library that you
88 want to copy in to the bundle. The "dest" attribute is
89 optional, as usual. Bundler will find all translations of that
90 library/program under the indicated directory and copy them.-->
91 <translations name="gtk30">
92 ${prefix}/share/locale
96 <!-- Data to copy in, usually Glade/UI files, images, sounds files
97 etc. The destination inside the bundle can be specified if the
98 files should end up at a different location, by using the
99 "dest" property. The destination must then start with the macro
100 "${bundle}", which refers to the bundle root directory.
103 ${prefix}/share/gtk-demo
106 <!-- Copy in the themes data. You may want to trim this to save space
109 ${prefix}/share/themes
113 ${prefix}/share/glib-2.0/schemas
116 <!-- Copy icons. Note that the .icns file is an Apple format which
117 contains up to 4 sizes of icon. You can use
118 /Developer/Applications/Utilities/Icon Composer.app to import
119 artwork and create the file. >
120 <data dest="${bundle}/Contents/Resources">
121 ${project}/Giggle.icns
124 <!-- This is where theme commands go. You can copy them in from your
125 theme of choice if they provide and example, or you can just
126 change the source path. -->
128 <data dest="${bundle}/Contents/Resources/etc/${gtkdir}/gtkrc">
132 <!-- Icon themes to copy. The "icons" property can be either of
133 "auto", "all", or "none". All or none should be
134 self-explanatory, while auto means that the script will try to
135 figure out which icons are needed. This is done by getting all
136 the strings from all copied binaries, and matching them against
137 icon names. To be safe, you should use "all". "none" is useful
138 if you want just the index.theme file but no icons, mostly
139 needed for the "hicolor" base theme.
141 <icon-theme icons="auto">
147 ${prefix}/lib/pango/${pkg:pango:pango_module_version}/modules/*.so