A Swift wrapper around pango-1.x that is largely auto-generated from gobject-introspection. For up to date (auto-generated) reference documentation, see https://rhx.github.io/SwiftPango/
What is new?
Version 11 introduces a new type system into
to ensure it has a representation of the underlying types.
This is necessary for Swift 5.3 onwards, which requires more stringent casts.
As a consequence, accessors can accept and return idiomatic Swift rather than
underlying types or pointers.
This means that a lot of the changes will be source-breaking for code that
was compiled against libraries built with earlier versions of
- Requires Swift 5.2 or later
- Wrapper code is now
@inlinableto enable the compiler to optimise away most of the wrappers
- Parameters and return types use more idiomatic Swift (e.g.
Refwrappers instead of pointers,
- Functions that take or return records now are templated instead of using the type-erased Protocol
ErrorTypehas been renamed
GLibErrorto ensure it neither clashes with
- Parameters or return types for records/classes now use the corresponding, lightweight Swift
Refwrapper instead of the underlying pointer
Normally, you don't build this package directly (but for testing you can - see 'Building' below), but you embed it into your own project. To use SwiftPango, you need to use the Swift Package Manager. After installing the prerequisites (see 'Prerequisites' below), add
SwiftPango as a dependency to your
Package.swift file, e.g.:
// swift-tools-version:5.2 import PackageDescription let package = Package(name: "MyPackage", dependencies: [ .package(url: "https://github.com/rhx/SwiftPango.git", .branch("master")), ], targets: [.target(name: "MyPackage", dependencies: ["Pango"])] )
At this stage, the Swift Package manager does not (yet) know how to run external programs such as
gir2swift. Therefore the easiest way to compile your project with SwiftPango is to use build scripts that do this for you and pass the necessary flags to the Swift Package manager (see the following section).
The demo applications come with build scripts that configure some environment variables and pass required arguments when calling
swift package, etc. The easiest way to get started is to clone one of the following projects, then copy all the
*.sh shell scripts into your own project. Also, if you want to be able to build a desktop app, create a
Resources folder, and copy (at least) the
Info.plist file as well:
- SwiftHelloGtk: this is a quick starting point for a simple gtk app that does not need any resources.
- SwiftHelloGtkBuilder: this is a good starting point for a more complex app that has user interface files (
*.ui) for GtkBuilder in its
To build your project, you then simply run
from within your project folder. On macOS, you can also build the project using Xcode instead. To do this, you need to create an Xcode project first, then open the project in the Xcode IDE:
./xcodegen.sh open MyPackage.xcodeproj
After that, use the (usual) Build and Test buttons to build/test this package. Please note that, at this stage, the Swift Package manager is not able to create App targets for Xcode (so to build a macOs app rather than just a command line executable, you still need to use the
build.sh script that calls
app-wrapper.sh to create the standalone app bundle).
To build, you need at least Swift 5.2 (Swift 5.3+ should work fine), download from https://swift.org/download/ -- if you are using macOS, make sure you have the command line tools installed as well). Test that your compiler works using
swift --version, which should give you something like
$ swift --version Apple Swift version 5.2.4 (swiftlang-1220.127.116.11 clang-118.104.22.168) Target: x86_64-apple-darwin19.6.0
on macOS, or on Linux you should get something like:
$ swift --version Swift version 5.2.5 (swift-5.2.4-RELEASE) Target: x86_64-unknown-linux-gnu
Pango 1.40 or higher
These Swift wrappers have been tested with pango-1.40, 1.42, 1.44, and 1.46 as well as glib-2.56, 2.58, 2.60, 2.62, and 2.64. They should work with higher versions, but YMMV. Also make sure you have
gobject-introspection and its
.gir files installed.
On Ubuntu 18.04 and 16.04, you can use the gtk that comes with the distribution. Just install with the
apt package manager:
sudo apt update sudo apt install libpango1.0-dev gir1.2-pango-1.0 gobject-introspection libgirepository1.0-dev libxml2-dev
If you prefer a newer version of gtk, you can also install it from the GNOME 3 Staging PPA (see https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging), but be aware that this can be a bit dangerous (as this removes packages that can be vital, particularly if you use a GNOME-based desktop), so only do this if you know what you are doing:
sudo add-apt-repository ppa:gnome3-team/gnome3-staging sudo apt update sudo apt dist-upgrade sudo apt install libpango1.0-dev gir1.2-pango-1.0 gobject-introspection libgirepository1.0-dev libxml2-dev
On Fedora 29, you can use the gtk that comes with the distribution. Just install with the
dnf package manager:
sudo dnf install pango-devel glib2-devel gobject-introspection-devel libxml2-devel
On macOS, you can install glib and Cairo using HomeBrew (for setup instructions, see http://brew.sh). Once you have a running HomeBrew installation, you can use it to install a native version of cairo:
brew update brew install pango glib glib-networking gobject-introspection pkg-config
Normally, you don't build this package directly, but you embed it into your own project (see 'Embedding' below). However, you can build and test this module separately to ensure that everything works. Make sure you have all the prerequisites installed (see above). After that, you can simply clone this repository and build the command line executable (be patient, this will download all the required dependencies and take a while to compile) using
git clone https://github.com/rhx/SwiftPango.git cd SwiftPango ./build.sh ./test.sh
On macOS, you can build the project using Xcode instead. To do this, you need to create an Xcode project first, then open the project in the Xcode IDE:
./xcodegen.sh open Pango.xcodeproj
After that, use the (usual) Build and Test buttons to build/test this package.
You can find reference documentation inside the docs folder.
This was generated using the jazzy tool.
If you want to generate your own documentation, matching your local installation,
you can use the
generate-documentation.sh script in the repository.
Unfortunately, at this stage jazzy only works on macOS (and crashes under Linux), so this will currently only work on a Mac.
Here are some common errors you might encounter and how to fix them.
Old Swift toolchain or Xcode
If you get an error such as
$ ./build.sh error: unable to invoke subcommand: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-package (No such file or directory)
this probably means that your Swift toolchain is too old. Make sure the latest toolchain is the one that is found when you run the Swift compiler (see above).
If you get an older version, make sure that the right version of the swift compiler is found first in your
PATH. On macOS, use xcode-select to select and install the latest version, e.g.:
sudo xcode-select -s /Applications/Xcode.app xcode-select --install