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>
16 <prefix name="installer-dir">${env:HOME}/moonshot/mac-client-installer/moonshot-ui/</prefix>
18 <!-- The project directory is the default location of the created
19 app. If you leave out the path, the current directory is
20 used. Note the usage of an environment variable here again.
22 <destination overwrite="yes">${prefix:installer-dir}</destination>
25 <!-- Not implemented yet (DMG image). -->
28 <!-- Comment this out to keep the install names in binaries -->
29 <!--<run-install-name-tool/>-->
31 <!-- Optionally specify a launcher script to use. If the
32 application sets up everything needed itself, like
33 environment variable, linker paths, etc, a launcher script is
34 not needed. If the source path is left out, the default
37 <launcher-script>${project}/launcher.sh</launcher-script >
39 <!-- Indicate the active gtk version to use. This is needed only
40 for gtk+-3.0 projects. -->
44 <!-- The special macro "${project}" refers to the directory where
45 this bundle file is located. The application name and bundle
46 identifier are taken from the plist file.
48 <plist>${project}/moonshot-ui.plist</plist>
50 <!-- <main-binary>${prefix:installer-dir}bin/moonshot</main-binary>-->
51 <main-binary>${prefix}/bin/moonshot</main-binary>
53 <!-- Copy in GTK+ modules. Note the ${gtkdir} macro, which expands
54 to the correct library subdirectory for the specified gtk
58 ${prefix}/lib/${gtkdir}/modules/*.so
61 <!-- Copy in GTK+ theme engines and print backends. Note the use of the
62 "${pkg:module:variable}" macro, which evaluates to a pkg-config
63 variable in the specified module. Note that any libraries that
64 binaries link to are also copied in automatically. Note also
65 the included ${gtk} macro, which gets the correct package name
68 ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/engines/*.so
71 ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/printbackends/*.so
74 <!-- Starting with 2.24, gdk-pixbuf installs into its own directory. -->
76 ${prefix}/lib/gdk-pixbuf-2.0/${pkg:${gtk}:gtk_binary_version}/*.so
80 <binary>${prefix}/bin/dbus-*</binary>
81 <!-- system.conf and session.conf -->
82 <data>${prefix}/etc/dbus-1</data>
83 <!-- org.janet.Moonshot.service -->
84 <data>${prefix}/share/dbus-1</data>
85 <binary>${prefix}/libexec/dbus-daemon-launch-helper</binary>
88 <!-- Translation filenames, one for each program or library that you
89 want to copy in to the bundle. The "dest" attribute is
90 optional, as usual. Bundler will find all translations of that
91 library/program under the indicated directory and copy them.-->
92 <translations name="gtk20">
93 ${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/moonshot-ui
106 <!-- Copy in the themes data. You may want to trim this to save space
108 <data>${prefix}/share/themes/Default</data>
111 <data dest="${bundle}/Contents/Resources">${project}/moonshot-ui.icns</data>
113 <!-- This is where theme commands go. You can copy them in from your
114 theme of choice if they provide and example, or you can just
115 change the source path. -->
117 <data dest="${bundle}/Contents/Resources/etc/${gtkdir}/gtkrc">
121 <!-- Icon themes to copy. The "icons" property can be either of
122 "auto", "all", or "none". All or none should be
123 self-explanatory, while auto means that the script will try to
124 figure out which icons are needed. This is done by getting all
125 the strings from all copied binaries, and matching them against
126 icon names. To be safe, you should use "all". "none" is useful
127 if you want just the index.theme file but no icons, mostly
128 needed for the "hicolor" base theme.
130 <icon-theme icons="all">