summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorAnthony Green <green@moxielogic.com>2018-03-14 11:13:32 -0400
committerAnthony Green <green@moxielogic.com>2018-03-14 11:13:32 -0400
commit076d5a987e016669993154b91525b02978c56727 (patch)
treef2a6d4a989360e16938932f564e4c5e8f8f9c32c /README.md
parentd2f7e788aecf37971c9be1cd650f78a3e4061e18 (diff)
downloadlibffi-076d5a987e016669993154b91525b02978c56727.tar.gz
markdown fixes
Diffstat (limited to 'README.md')
-rw-r--r--README.md64
1 files changed, 31 insertions, 33 deletions
diff --git a/README.md b/README.md
index 89767ea..cad04ff 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,6 @@
Status
======
-THIS IS A WORK IN PROGRESS..
-
[![Build Status](https://travis-ci.org/libffi/libffi.svg?branch=master)](https://travis-ci.org/libffi/libffi)
[![Build status](https://ci.appveyor.com/api/projects/status/8lko9vagbx4w2kxq?svg=true)](https://ci.appveyor.com/project/atgreen/libffi)
@@ -157,7 +155,7 @@ It's also possible to build libffi on Windows platforms with
Microsoft's Visual C++ compiler. In this case, use the msvcc.sh
wrapper script during configuration like so:
-path/to/configure CC=path/to/msvcc.sh CXX=path/to/msvcc.sh LD=link CPP="cl -nologo -EP"
+ path/to/configure CC=path/to/msvcc.sh CXX=path/to/msvcc.sh LD=link CPP="cl -nologo -EP"
For 64-bit Windows builds, use CC="path/to/msvcc.sh -m64" and
CXX="path/to/msvcc.sh -m64". You may also need to specify --build
@@ -166,7 +164,7 @@ appropriately.
It is also possible to build libffi on Windows platforms with the LLVM
project's clang-cl compiler, like below:
-path/to/configure CC="path/to/msvcc.sh -clang-cl" CXX="path/to/msvcc.sh -clang-cl" LD=link CPP="clang-cl -EP"
+ path/to/configure CC="path/to/msvcc.sh -clang-cl" CXX="path/to/msvcc.sh -clang-cl" LD=link CPP="clang-cl -EP"
When building with MSVC under a MingW environment, you may need to
remove the line in configure that sets 'fix_srcfile_path' to a 'cygpath'
@@ -408,35 +406,35 @@ Thorup.
Major processor architecture ports were contributed by the following
developers:
-aarch64 Marcus Shawcroft, James Greenhalgh
-alpha Richard Henderson
-arm Raffaele Sena
-blackfin Alexandre Keunecke I. de Mendonca
-cris Simon Posnjak, Hans-Peter Nilsson
-frv Anthony Green
-ia64 Hans Boehm
-m32r Kazuhiro Inaoka
-m68k Andreas Schwab
-m88k Miod Vallat
-microblaze Nathan Rossi
-mips Anthony Green, Casey Marshall
-mips64 David Daney
-moxie Anthony Green
-nios ii Sandra Loosemore
-openrisc Sebastian Macke
-pa Randolph Chung, Dave Anglin, Andreas Tobler
-powerpc Geoffrey Keating, Andreas Tobler,
- David Edelsohn, John Hornkvist
-powerpc64 Jakub Jelinek
-s390 Gerhard Tonn, Ulrich Weigand
-sh Kaz Kojima
-sh64 Kaz Kojima
-sparc Anthony Green, Gordon Irlam
-tile-gx/tilepro Walter Lee
-vax Miod Vallat
-x86 Anthony Green, Jon Beniston
-x86-64 Bo Thorsen
-xtensa Chris Zankel
+ aarch64 Marcus Shawcroft, James Greenhalgh
+ alpha Richard Henderson
+ arm Raffaele Sena
+ blackfin Alexandre Keunecke I. de Mendonca
+ cris Simon Posnjak, Hans-Peter Nilsson
+ frv Anthony Green
+ ia64 Hans Boehm
+ m32r Kazuhiro Inaoka
+ m68k Andreas Schwab
+ m88k Miod Vallat
+ microblaze Nathan Rossi
+ mips Anthony Green, Casey Marshall
+ mips64 David Daney
+ moxie Anthony Green
+ nios ii Sandra Loosemore
+ openrisc Sebastian Macke
+ pa Randolph Chung, Dave Anglin, Andreas Tobler
+ powerpc Geoffrey Keating, Andreas Tobler,
+ David Edelsohn, John Hornkvist
+ powerpc64 Jakub Jelinek
+ s390 Gerhard Tonn, Ulrich Weigand
+ sh Kaz Kojima
+ sh64 Kaz Kojima
+ sparc Anthony Green, Gordon Irlam
+ tile-gx/tilepro Walter Lee
+ vax Miod Vallat
+ x86 Anthony Green, Jon Beniston
+ x86-64 Bo Thorsen
+ xtensa Chris Zankel
Jesper Skov and Andrew Haley both did more than their fair share of
stepping through the code and tracking down bugs.