+++ /dev/null
-<?xml version="1.0" standalone="no"?> <!--*- mode: xml -*-->
-<app-bundle>
-
- <meta>
- <!-- Where to pick up the GTK+ installation, icon themes,
- etc. Note that "${env:JHBUILD_PREFIX}" is evaluated to the
- value of the environment variable JHBUILD_PREFIX. You can
- define additional prefixes and refer to them in paths
- throughout this file on the form "${prefix:name}". This is
- useful for installing certain libraries or even the
- application itself separately. Note that JHBUILD_PREFIX is
- defined by jhbuild, so it you are not using jhbuild you can
- either define your own or just hardcode the path here.
- -->
- <prefix name="default">${env:JHBUILD_PREFIX}</prefix>
- <prefix name="installer-dir">${env:HOME}/moonshot/mac-client-installer/moonshot-ui/</prefix>
- <prefix name="dbus-source-dir">${env:HOME}/gtk/source/dbus-1.4.16/</prefix>
-
- <!-- The project directory is the default location of the created
- app. If you leave out the path, the current directory is
- used. Note the usage of an environment variable here again.
- -->
- <destination overwrite="yes">${prefix:installer-dir}</destination>
-
- <image>
- <!-- Not implemented yet (DMG image). -->
- </image>
-
- <!-- Comment this out to keep the install names in binaries -->
- <!--<run-install-name-tool/>-->
-
- <!-- Optionally specify a launcher script to use. If the
- application sets up everything needed itself, like
- environment variable, linker paths, etc, a launcher script is
- not needed. If the source path is left out, the default
- script will be used.
- -->
- <launcher-script>${project}/launcher.sh</launcher-script >
-
- <!-- Indicate the active gtk version to use. This is needed only
- for gtk+-3.0 projects. -->
- <gtk>gtk+-2.0</gtk>
- </meta>
-
- <!-- The special macro "${project}" refers to the directory where
- this bundle file is located. The application name and bundle
- identifier are taken from the plist file.
- -->
- <plist>${project}/moonshot-ui.plist</plist>
-
- <!-- <main-binary>${prefix:installer-dir}bin/moonshot</main-binary>-->
- <main-binary>${prefix}/bin/moonshot</main-binary>
-
- <!-- Copy in GTK+ modules. Note the ${gtkdir} macro, which expands
- to the correct library subdirectory for the specified gtk
- version.
- -->
- <binary>
- ${prefix}/lib/${gtkdir}/modules/*.so
- </binary>
-
- <!-- Copy in GTK+ theme engines and print backends. Note the use of the
- "${pkg:module:variable}" macro, which evaluates to a pkg-config
- variable in the specified module. Note that any libraries that
- binaries link to are also copied in automatically. Note also
- the included ${gtk} macro, which gets the correct package name
- to get. -->
- <binary>
- ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/engines/*.so
- </binary>
- <binary>
- ${prefix}/lib/${gtkdir}/${pkg:${gtk}:gtk_binary_version}/printbackends/*.so
- </binary>
-
-<!-- Starting with 2.24, gdk-pixbuf installs into its own directory. -->
- <binary>
- ${prefix}/lib/gdk-pixbuf-2.0/${pkg:${gtk}:gtk_binary_version}/*.so
- </binary>
-
-<!-- DBUS -->
- <binary>${prefix}/bin/dbus-*</binary>
- <!-- org.janet.Moonshot.service -->
- <data>${prefix}/share/dbus-1</data>
- <binary>${prefix}/libexec/dbus-daemon-launch-helper</binary>
- <data dest="${bundle}/Contents/Resources/etc/dbus-1/session.d/">${prefix:dbus-source-dir}/test/data/valid-config-files/session.d/</data>
- <!-- session.conf: we're not shipping system.conf -->
- <data dest="${bundle}/Contents/Resources/etc/dbus-1/session.conf">${prefix:dbus-source-dir}/bus/session.conf</data>
-
-
- <!-- Translation filenames, one for each program or library that you
- want to copy in to the bundle. The "dest" attribute is
- optional, as usual. Bundler will find all translations of that
- library/program under the indicated directory and copy them.-->
- <translations name="gtk20">
- ${prefix}/share/locale
- </translations>
-
- <!-- Data to copy in, usually Glade/UI files, images, sounds files
- etc. The destination inside the bundle can be specified if the
- files should end up at a different location, by using the
- "dest" property. The destination must then start with the macro
- "${bundle}", which refers to the bundle root directory.
- -->
- <!-- data>
- ${prefix}/share/moonshot-ui
- </data -->
-
- <!-- Copy in the themes data. You may want to trim this to save space
- in your bundle. -->
- <data>${prefix}/share/themes/Default</data>
-
- <!-- App icon -->
- <data dest="${bundle}/Contents/Resources">${project}/moonshot-ui.icns</data>
-
- <!-- This is where theme commands go. You can copy them in from your
- theme of choice if they provide and example, or you can just
- change the source path. -->
-
- <data dest="${bundle}/Contents/Resources/etc/${gtkdir}/gtkrc">
- ${project}/gtkrc
- </data>
-
- <!-- Icon themes to copy. The "icons" property can be either of
- "auto", "all", or "none". All or none should be
- self-explanatory, while auto means that the script will try to
- figure out which icons are needed. This is done by getting all
- the strings from all copied binaries, and matching them against
- icon names. To be safe, you should use "all". "none" is useful
- if you want just the index.theme file but no icons, mostly
- needed for the "hicolor" base theme.
- >-->
- <icon-theme icons="all">
- Tango
- </icon-theme>
-
-</app-bundle>
projects / moonshot-ui.git / blobdiff