Commit 5d2ccbec authored by Richard Hult's avatar Richard Hult

Initial commit

parents
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
PACKAGE = ige-mac-bundler
VERSION = 0.1
bindir=$(HOME)/bin
all:
@echo 'Run "make install" to install.'
install:
@mkdir -p $(bindir)
@sed "s,@PATH@,`pwd`,g" < ige-mac-bundler.in > $(bindir)/ige-mac-bundler
@chmod a+x $(bindir)/ige-mac-bundler
distdir = $(PACKAGE)-$(VERSION)
dist:
-rm -rf $(distdir)
mkdir $(distdir)
cp -p README COPYING NEWS Makefile ige-mac-bundler.in launcher.sh *.py $(distdir)/
mkdir $(distdir)/examples
cp -p examples/* $(distdir)/examples/
chmod -R a+r $(distdir)
tar czf $(distdir).tar.gz $(distdir)
rm -rf $(distdir)
.PHONY: all install
Ige Mac Bundler
===============
The script ige-mac-bundler is a helper script that creates application
bundles form GTK+ executables for Mac OS X. The resulting bundle will
contain a complete self-hosting GTK+ installation, ready to run on any
computer with Mac OS X 10.4 or later installed.
GTK+ and its companion libraries are automatically put into the
bundle, but the application packager must tell the script what other
files and directories to copy.
Setting up
----------
Run "make install"; this installs the script into ~/bin. Make sure you
have that directory in your path, or use the full path when starting
the script.
Prerequisites
-------------
You need to have a GTK+ installation as done for example by using
jhbuild as described on the GTK+ OS X project site:
http://developer.imendio.com/projects/gtk-macosx/build-instructions
[ Note that at the time of writing you need to patch Pango to support
path-relative modules, see:
http://bugzilla.gnome.org/show_bug.cgi?id=454017 ]
The ige-mac-bundler command needs to be ran inside an environment
setup for running the GTK+, for example inside a jhbuild shell.
For the more in-depth parts described here, you are expected to be
familiar with the layout of OS X bundles.
Quick introduction
------------------
You need to create a configuration file describing the application
bundle. The very simple example, example.bundle:
<?xml version="1.0"?> <!--*- mode: xml -*-->
<app-bundle>
<meta>
<prefix>/opt/gtk</prefix>
</meta>
<plist>${project}/Info.plist</plist>
<launcher-script>yes</launcher-script>
<!-- The executable for the application -->
<main-binary>${prefix}/bin/my-app</main-binary>
<!-- Modules for GTK+ and Pango (font rendering, image loaders, etc) -->
<binary>${prefix}/lib/gtk-2.0</binary>
<binary>${prefix}/lib/pango</binary>
<!-- Any additional data, like images, or Glade files -->
<data>
${prefix}/share/my-app
</data>
</app-bundle>
Put this file into a directory, together with the standard Info.plist
file that all Mac OS X bundles need. Then run the script with the
bundle configuration path as argument. This will create a bundle in
the current directory.
The file format in more depth
=============================
The simple example above works for small and simple applications, but
often you will need to specify more data to copy in, or to have more
detailed control over what is copied.
Here we go through in more depth how this can be acheived. Every file
and directory to copy is specified with a source path, and an optional
destination path. An example that copies an entire directory
recursively, from the installation prefix:
<data>
${prefix}/share/my-data
</data>
Since no destination path is specified, the directory will be copied
into the standard location. Note that the special value ${prefix} is
used in the source path, which makes the default destination path be
relative to the "bundle prefix", which is the Contents/Resources
directory inside the bundle. Applications that use the freedesktop
"data dir" specification to find their data will automatically find
its data this way (applications can also use the Carbon or Cocoa
bundle APIs to find data).
Another useful "special value" that can be used in source paths is
${project}, which refers to the directory where the XML file is
located. An example:
<data dest="${bundle}/Contents/Resources/etc/gtk-2.0/gtkrc">
${project}/gtkrc
</data>
Here you notice that a destination path is supplied. This must be done
since there is no way to figure out where to put the file that doesn't
come from a ${prefix} location. You can also see another variable
used, this time in the destination path, ${bundle}. All destination
paths must be either unset or start with ${bundle}.
The remaining variables, are:
${env:name} - evaluates to the environment variable "name"
${pkg:module:name} - evaluates to the value of the pkg-config
variable "name" in the module "module"
An example use case of the latter is for finding files that are
located in a versioned directory without having to maintain the
directory name manually. For example:
<binary>
${prefix}/lib/gtk-2.0/${pkg:gtk+-2.0:gtk_binary_version}/loaders
</binary>
Metadata
--------
Now that we know how paths can be specified, let's back up and see the
beginning of a more extensive exampe. The first thing to setup is some
metadata:
<app-bundle>
<meta>
<prefix name="default">${env:PREFIX}</prefix>
<destination overwrite="yes">${env:HOME}/Desktop</destination>
</meta>
[...]
</app-bundle>
We use the ${env} variable to get the installation prefix (which comes
from the jhbuild build script). We also use it to set the destination
of the app bundle on the current user's desktop.
You can set additional prefixes and refer to them in paths:
<meta>
<prefix name="default">${env:PREFIX}</prefix>
<prefix name="gst">/opt/gstreamer</prefix>
<prefix name="stuff">/opt/stuff</prefix>
</meta>
The additional prefixes are referred to by using ${prefix:name}, where
"name" is one of the names defined above.
Installed data
--------------
Next you need to list the data to install. Some is required for the
app bundle to be complete:
<plist>${project}/../data/Info.plist</plist>
<launcher-script>${project}/launcher.sh</launcher-script>
<main-binary>${prefix}/bin/giggle</main-binary>
The file Info.plist is the standard Mac OS file for bundles. See XXX
for documentation on those.
The launcher script is used to setup the necessary environment for the
application to work. If your application does this itself, you can
leave it out. Many applications will work out of the box with the
launcher script though. If no script is specified in the tag, a
default one is used, that sets up the needed environent for most GTK+
applications.
Unsurprisingly, the main-binary tag specifies the executable to launch
when starting the application.
General application data
------------------------
Next we handle any general data to copy into the bundle. A
straight-forward example:
<data dest="${bundle}/Contents/Resources">
${project}/Giggle.icns
</data>
<data dest="${bundle}/Contents/Resources/etc/gtk-2.0/gtkrc">
${project}/gtkrc
</data>
Binaries
--------
When it comes to binaries (executables and loadable modules), the tag
"binary" should be used. The difference between "binary" and "data" is
that all copied binaries are scanned for library dependencies, which
are automatically copied into the bundle. This way, you only need to
list your executables and plugins. Again, an example:
<binary>
${prefix}/lib/pango/${pkg:pango:pango_module_version}/modules/pango-basic-atsui.so
</binary>
This will copy the ATSUI font module for Pango. This in turn will pull
in any needed libraries that it links to.
Note that you can use wildcards for all data and binary tags, for
example:
<binary>
${prefix}/lib/gtk/*/*/*.so
</binary>
Icon themes
-----------
GTK+ icon themes have their own tag, "icon-theme". The name of the
theme (which currently must reside in the default prefix) specifies
which theme to copy, and the "icons" property specifies which icons to
copy. The valid values are:
auto - tries to copy all icons names that match strings in all
copied binaries; this will not always work perfectly but is
good for getting started, and for simple applications
all - copies all icons
none - copies no icons, this can be used in combination with
specifying icons manually with a regular data tag; the icon
theme itself must be listed in order to get the index theme
copied and an icon cache generated
Note that the base theme "hicolor" is always copied, since it is
required by GTK+. An example:
<icon-theme icons="auto">
Tango
</icon-theme>
Unimplemented so far
--------------------
- Translations - you can copy them manually using the data tag
- Built-in support for PyGTK or Mono applications
- Using install_name_tool instead of relying on DYLD_*
Debugging the bundle
====================
In order to debug the created app bundle (most notably the launcher
script), you can set the environment variable IGE_MAC_APP_DEBUG before
starting the applications directly from a terminal. e.g.:
IGE_MAC_APP_DEBUG=yes MyApp.app/Contents/MacOS/MyApp
This will print out the steps performed by the launcher script before
the application executable is started.
Note also that the Console.app program that comes with OS X is very
useful when debugging app bundle problems. You can use it to see any
output from the application the console log window.
License
=======
The script is licensed under the GNU General Public License version
2. The resulting bundle created by the script is not covered by that
and can be licensed any way you want.
import sys
import os, errno, glob
import dircache, shutil
import re
from plistlib import Plist
from sets import Set
from distutils import dir_util
from project import *
import utils
class Bundler:
def __init__(self, project):
self.project = project
self.project_dir = project.get_project_dir()
plist_path = self.project.get_plist_path()
self.plist = Plist.fromFile(plist_path)
# List of paths that should be recursively searched for
# binaries that are used to find library dependencies.
self.binary_paths = []
# Create the bundle in a temporary location first and move it
# to the final destination when done.
dest = project.get_meta().dest
self.bundle_path = os.path.join(dest, "." + project.get_name() + ".app")
def recursive_rm(self, dirname):
# Extra safety ;)
if dirname in [ "/", os.getenv("HOME"), os.path.join(os.getenv("HOME"), "Desktop") ]:
raise "Eek, trying to remove a bit much, eh? (%s)" % (dirname)
if not os.path.exists(dirname):
return
files = dircache.listdir(dirname)
for file in files:
path = os.path.join (dirname, file)
if os.path.isdir(path):
self.recursive_rm(path)
else:
retval = os.unlink(path)
os.rmdir(dirname)
def create_skeleton(self):
utils.makedirs(self.project.get_bundle_path("Contents/Resources"))
utils.makedirs(self.project.get_bundle_path("Contents/MacOS"))
def create_pkglist(self):
path = self.project.get_bundle_path("Contents", "PkgInfo")
path = self.project.evaluate_path(path)
f = open (path, "w")
f.write(self.plist.CFBundleSignature)
f.close()
def copy_plist(self):
path = Path(self.project.get_plist_path(),
self.project.get_bundle_path("Contents"))
self.copy_path(path)
def create_pango_setup(self):
# Create a temporary pangorc file just for creating the
# modules file with the right modules.
modulespath = self.project.get_bundle_path("Contents/Resources/lib/pango/" +
"${pkg:pango:pango_module_version}/"+
"modules")
import tempfile
fd, tmp_filename = tempfile.mkstemp()
f = os.fdopen(fd, "w")
f.write("[Pango]\n")
f.write("ModulesPath=" + utils.evaluate_pkgconfig_variables (modulespath))
f.write("\n")
f.close()
cmd = "PANGO_RC_FILE=" + tmp_filename + " pango-querymodules"
f = os.popen(cmd)
path = self.project.get_bundle_path("Contents/Resources/etc/pango")
utils.makedirs(path)
fout = open(os.path.join(path, "pango.modules"), "w")
prefix = self.project.get_bundle_path("Contents/Resources")
for line in f:
line = line.strip()
if line.startswith("#"):
continue
# Replace the hardcoded bundle path with @executable_path...
if line.startswith(prefix):
line = line[len(prefix):]
line = "@executable_path/../Resources" + line
fout.write(line)
fout.close()
os.unlink(tmp_filename)
# Create the final pangorc file
path = self.project.get_bundle_path("Contents/Resources/etc/pango")
utils.makedirs(path)
f = open(os.path.join(path, "pangorc"), "w")
f.write("[Pango]\n")
f.write("ModuleFiles=./pango.modules\n")
f.close()
def create_gtk_immodules_setup(self):
path = self.project.get_bundle_path("Contents/Resources")
cmd = "GTK_EXE_PREFIX=" + path + " gtk-query-immodules-2.0"
f = os.popen(cmd)
path = self.project.get_bundle_path("Contents/Resources/etc/gtk-2.0")
utils.makedirs(path)
fout = open(os.path.join(path, "gtk.immodules"), "w")
prefix = "\"" + self.project.get_bundle_path("Contents/Resources")
for line in f: