commit 28682b1be12457fae676f258bd53f052cbd33b45
parent b399b7c97d3b9b13b2046c8c4dc9518d074be1d3
Author: ByteProject <ByteProject@users.noreply.github.com>
Date: Sat, 22 Apr 2017 18:16:18 +0200
extensive README update
Diffstat:
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/README.md b/README.md
@@ -20,11 +20,11 @@ This is a complete rewrite of [AnsiLove/PHP](https://www.ansilove.org) in the C
# Specs
-AnsiLove/C is strictly using the `C99 standard` to achieve high portability to all major operating systems. Supported compilers are `GCC` and `Clang`, others may work but aren't tested. We use Linux, OpenBSD and Mac OS X for AnsiLove/C development.
+AnsiLove/C is strictly using the `C99 standard` to achieve high portability to all major operating systems. Supported compilers are `GCC` and `Clang`, others may work but aren't tested. We use Linux and OpenBSD for AnsiLove/C development.
# Why C?
-There were many reasons, most notably PHP interpreter independence and performance. A solid C foundation is just perfect for creating libraries and frameworks and it can easily be embedded into applications. We already mentioned portability. What else? We wanted evolution. AnsiLove/C should not be understood as a port. It takes many different approaches (like processing binary font dumps or generating @2x Retina images), it is overall improved and introduces new features. While results tend to be the same, the codebase does not have much in common with it's ancestor.
+There were many reasons, most notably PHP interpreter independence and performance. A solid C foundation is just perfect for creating libraries and it can easily be embedded into applications. We already mentioned portability. What else? We wanted evolution. AnsiLove/C should not be understood as a port. It takes many different approaches (like processing binary font dumps or generating @2x Retina images), it is overall improved and introduces new features. While results tend to be the same, the codebase does not have much in common with it's ancestor.
# Dependencies
@@ -37,7 +37,7 @@ AnsiLove/C uses the `CMake` build system and requires the `GD` library and heade
- FreeBSD: `pkg add cmake gd`
- Mac OS X: `brew install cmake gd`
- Alpine Linux: `apk add cmake gcc make musl-dev gd-dev`
-- Debian / Ubuntu: `apt-get install cmake libgd-dev`
+- Debian / Ubuntu / Mint: `apt-get install cmake libgd-dev`
- Solus: `eopkg install -c system.devel` and `eopkg install gd-devel`
# Compiling
@@ -45,6 +45,8 @@ AnsiLove/C uses the `CMake` build system and requires the `GD` library and heade
cmake .
make
+You can also build the project directly from [Atom](https://atom.io). Note that the [Atom Build](https://atom.io/packages/build) package is necessary for this purpose.
+
# Installation
AnsiLove/C packages are available for:
@@ -65,10 +67,6 @@ AnsiLove/C packages are available for:
eopkg install ansilove
-# Cocoa
-
-If you're looking for something to implement into your Cocoa applications, we highly recommend taking a look at [AnsiLove.framework](https://github.com/ansilove/AnsiLove.framework).
-
# Features
Rendering of all known ANSi / ASCII art file types:
@@ -209,5 +207,9 @@ AnsiLove/C is released under the BSD 2-Clause License. See the file `LICENSE` fo
GitHub: https://github.com/ansilove/ansilove
+# MacOS framework
+
+If you're looking for something to implement into your MacOS applications, you might want to have a look at [AnsiLove.framework](https://github.com/ansilove/AnsiLove.framework). The codebase is still Cocoa, which is bad in a world that obviously moved on to Swift. The framework is not actively maintained anymore and thus considered deprecated. Drop us an email in case you're interested in taking over.
+
[1]: https://api.travis-ci.org/ansilove/ansilove.png?branch=master
[2]: https://travis-ci.org/ansilove/ansilove
