Skip to content

Add missing steps to creating a C library package. #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 20, 2015
Merged

Add missing steps to creating a C library package. #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions Documentation/SystemModules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,17 @@ typically always refer to it that way. A good rule of thumb is to look at the he
see the header is called simply "ogg.h". Pay attention to capitalization; note that we provide `CPOSIX` and not
`CPosix`, because POSIX is an acronym and is typically spelled all-caps.

We also need to create an empty Package.swift file to let the package
manager know `CVorbis` is a package. Finally, we need to initialize
this directory as a Git repository, adding all the files we created,
and tagging it with a version number for the package manager to use:

CVorbis$ touch Package.swift
CVorbis$ git init
CVorbis$ git add .
CVorbis$ git ci -m "Creating module package"
CVorbis$ git tag 1.0.0

Back in our example app we need a `Package.swift` that depends on CVorbis:

```swift
Expand Down