Book Image

Mastering Swift 3 - Linux

By : Jon Hoffman
Book Image

Mastering Swift 3 - Linux

By: Jon Hoffman

Overview of this book

Swift is a modern, fast, and safe programming language created by Apple. Writing Swift is interactive and fun, the syntax is concise yet expressive, and the code runs lightning-fast. Swift’s move to open source has been embraced with open arms and has seen increased adoption in the Linux platform. Our book will introduce you to the Swift language, further delving into all the key concepts you need to create applications for desktop, server, and embedded Linux platforms. We will teach you the best practices to design an application with Swift 3 via design patterns and Protocol-Oriented Programming. Further on, you will learn how to catch and respond to errors within your application. When you have gained a strong knowledge of using Swift in Linux, we’ll show you how to build IoT and robotic projects using Swift on single board computers. By the end of the book, you will have a solid understanding of the Swift Language with Linux and will be able to create your own applications with ease.
Table of Contents (24 chapters)
Mastering Swift 3 - Linux
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
2
Learning About Variables, Constants, Strings, and Operators

Creating a custom module


To create a custom module, we will begin by creating a directory to put all of its files in. This will be the module's main directory. Within this directory, we will need two files. The first is a file named Package.swift, and the second is named module.modulemap.

Within the module.modulemap file we will define the headers we want to import and the libraries that we wish to link to. The following sample shows how the module.modulemap file is formatted:

module CMyModule [system] { 
  header "/usr/include/mylibheader.h" 
  link "mylib" 
  export * 
} 

The first line defines the name of the module. This name is what we will import in our Swift files. In this sample, the module's name is CMyModule. The next line defines the full path to the header file that we want to import. The third line is optional and tells the compiler that the functionality defined in the header can be found in the mylib library, so we will need to link it. If we do not...