1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
What is ObjFW?
==============
[ObjFW](https://objfw.nil.im/) is a portable, lightweight framework for the
Objective-C language. It enables you to write an application in Objective-C
that will run on any [platform](PLATFORMS.md) supported by ObjFW without having
to worry about differences between operating systems or various frameworks you
would otherwise need if you want to be portable.
It supports all modern Objective-C features when using Clang, but is also
compatible with GCC ≥ 4.6 to allow maximum portability.
ObjFW is intentionally incompatible with Foundation. This has two reasons:
* GNUstep already provides a reimplementation of Foundation, which is only
compatible to a certain degree. This means that a developer still needs to
care about differences between frameworks if they want to be portable. The
idea behind ObjFW is that developers do not need to concern themselves with
portability and making sure their code works with multiple frameworks:
Instead, if it works with ObjFW on one platform, they can reasonably expect
it to also work with ObjFW on another platform. ObjFW behaving differently
on different operating systems (unless inevitable because it is a
platform-specific part, like the Windows Registry) is considered a bug and
will be fixed.
* Foundation predates a lot of modern Objective-C concepts. The most prominent
one is exceptions, which are only used in Foundation as a replacement for
`abort()`. This results in cumbersome error handling, especially in
initializers, which in Foundation only return `nil` on error with no
indication of what went wrong. It also means that the return of every `init`
call needs to be checked against `nil`. But in the wild, nobody actually
checks *each and every* return from `init` against `nil`, leading to bugs.
ObjFW fixes this by making exceptions a first class citizen.
You can read more about the differences to Foundation
[here](https://git.nil.im/ObjFW/ObjFW/wiki/Differences-to-Foundation).
ObjFW also comes with its own lightweight and extremely fast Objective-C
runtime, which in real world use cases was found to be significantly faster
than both GNU's and Apple's runtime.
Installation
============
You can either follow the [instructions](INSTALLATION.md) to install ObjFW or
you can [build ObjFW from source](COMPILING.md).
Usage
=====
To create your first, empty application, you can use `objfw-new`:
objfw-new --app MyFirstApp
This creates a file `MyFirstApp.m`. The `-[applicationDidFinishLaunching:]`
method is called as soon as ObjFW finished all initialization. Use this as the
entry point to your own code. For example, you could add the following line
there to create a "Hello World":
[OFStdOut writeLine: @"Hello World!"];
You can compile your new app using `objfw-compile`:
objfw-compile -o MyFirstApp MyFirstApp.m
`objfw-compile` is a tool that allows building applications and libraries using
ObjFW without needing a full-blown build system. If you want to use your own
build system, you can get the necessary flags from `objfw-config`.
Documentation
=============
You can find the documentation for the latest released version of ObjFW
[here](https://objfw.nil.im/docs/).
In order to build the documentation yourself (necessary to have documentation
for trunk / master), you need to have [Doxygen](https://www.doxygen.nl)
installed. Once installed, you can build the documentation from the root
directory of the repository:
make docs
License
=======
ObjFW is released under the GNU Lesser General Public License version 3.0.
If this license does not work for you, contact me and we can find a solution.
Bugs and feature requests
=========================
If you find any bugs or have feature requests, please
[file a new bug](https://git.nil.im/ObjFW/ObjFW/issues/new/choose) in the
[bug tracker](https://git.nil.im/ObjFW/ObjFW/issues).
Alternatively, feel free to send a mail to js@nil.im!
Support and community
=====================
If you have any questions about ObjFW or would like to talk to other ObjFW
users, the following venues are available:
* A [discussions repository](https://git.nil.im/ObjFW/discussions) in which
you can open an issue to start a discussion topic
* A [Matrix room](https://matrix.to/#/%23objfw:nil.im)
* A [Discord room](https://objfw.nil.im/discord), bridged to the Matrix room
above
* A [Signal room](https://objfw.nil.im/signal), bridged to the Matrix room
above
* A [Telegram room](https://t.me/objfw), bridged to the Matrix room above
* A [Slack room](https://objfw.nil.im/slack), bridged to the Matrix room above
* An IRC channel named `#objfw` on `irc.libera.chat`
Please don't hesitate to join any or all of those!
Donating
========
If you want to donate to ObjFW, you can read about possible ways to do so
[here](DONATING.md).
Thanks
======
* Thank you [Jonathan Neuschäfer](https://github.com/neuschaefer) for
reviewing the *entirety* (all 84k LoC at the time) of ObjFW's codebase in
2017!
* Thank you [Hill Ma](https://github.com/mahiuchun) for donating an M1 Mac
Mini to the project in 2022!
|
