Cleanups, moving namespaces
[gmpc.git] / mac / gmpc.bundle
blob85e1765539f4edfaeb9b05f695dfb96db7364b63
1 <?xml version="1.0" standalone="no"?> <!--*- mode: xml -*-->
2 <app-bundle>
4 <meta>
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.
14 -->
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.
20 -->
21 <destination overwrite="yes">${env:HOME}/Desktop</destination>
23 <image>
24 <!-- Not implemented yet (DMG image). -->
25 </image>
27 <!-- Optionally specify a launcher script to use. If the
28 application sets up everything needed itself, like
29 environment variable, linker paths, etc, a launcher script is
30 not needed. If the source path is left out, the default
31 script will be used.
32 -->
33 <!--launcher-script>${project}/launcher.sh</launcher-script-->
35 <!-- Not implemented: Optional runtime, could be python or mono
36 for example.
37 -->
38 <!--runtime copy="yes">/usr/bin/python</runtime-->
39 </meta>
41 <!-- The special macro "${project}" refers to the directory where
42 this bundle file is located. The application name and bundle
43 identifier are taken from the plist file.
44 -->
45 <plist>${project}/Info.plist</plist>
47 <main-binary>${prefix}/bin/gmpc</main-binary>
49 <!-- Copy in GTK+ modules. Note the use of the
50 "${pkg:module:variable}" macro, which evaluates to a pkg-config
51 variable in the specified module. Note that any libraries that
52 binaries link to are also copied in automatically.
53 -->
54 <binary>
55 ${prefix}/lib/libglade*
56 </binary>
57 <binary>
58 ${prefix}/lib/libige*
59 </binary>
60 <binary>
61 ${prefix}/lib/libsexy*
62 </binary>
63 <binary>
64 ${prefix}/lib/libmpd.*
65 </binary>
66 <binary>
67 ${prefix}/lib/gtk-2.0/${pkg:gtk+-2.0:gtk_binary_version}/loaders/*.so
68 </binary>
70 <!-- Data to copy in, usually Glade/UI files, images, sounds files
71 etc. The destination inside the bundle can be specified if the
72 files should end up at a different location, by using the
73 "dest" property. The destination must then start with the macro
74 "${bundle}", which refers to the bundle root directory.
75 -->
76 <data>
77 ${prefix}/share/gmpc
78 </data>
80 <data dest="${bundle}/Contents/Resources">
81 ${project}/GMPC.icns
82 </data>
84 <data dest="${bundle}/Contents/Resources/etc/gtk-2.0/gtkrc">
85 ${project}/gtkrc
86 </data>
88 <!-- Icon themes to copy. The "icons" property can be either of
89 "auto", "all", or "none". All or none should be
90 self-explanatory, while auto means that the script will try to
91 figure out which icons are needed. This is done by getting all
92 the strings from all copied binaries, and matching them against
93 icon names. To be safe, you should use "all". "none" is useful
94 if you want just the index.theme file but no icons, mostly
95 needed for the "hicolor" base theme.
96 -->
97 <icon-theme icons="all">
98 hicolor
99 </icon-theme>
101 </app-bundle>