-
Notifications
You must be signed in to change notification settings - Fork 737
Improve README readability #639
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.
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
base: master
Are you sure you want to change the base?
Conversation
- Make important keywords italic
- Links are now parsed as links
- Highlights some specific words (e.g lib names, and directories)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for spending the time to improve this. I really appreciate it. Please see my comments.
README.md
Outdated
|
||
|
||
What is libffi? | ||
=============== | ||
|
||
Compilers for high level languages generate code that follow certain | ||
conventions. These conventions are necessary, in part, for separate | ||
compilation to work. One such convention is the "calling | ||
convention". The "calling convention" is essentially a set of | ||
compilation to work. One such convention is the *"calling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should remove the double quotes.
README.md
Outdated
@@ -127,17 +127,17 @@ Installing libffi | |||
|
|||
First you must configure the distribution for your particular | |||
system. Go to the directory you wish to build libffi in and run the | |||
"configure" program found in the root directory of the libffi source | |||
`"configure"` program found in the root directory of the libffi source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, please remove the double quotes.
|
||
You may want to tell configure where to install the libffi library and | ||
header files. To do that, use the ``--prefix`` configure switch. Libffi | ||
will install under /usr/local by default. | ||
will install under `/usr/local` by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a markdown expert, but I noticed that I used double backticks above for --prefix
. What is the difference between single and double backticks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not much difference. But i just thought it was most common to use single backticks in markdown
To build static library for ARM64 with MSVC using visual studio solution, msvc_build folder have | ||
aarch64/Ffi_staticLib.sln | ||
required header files in aarch64/aarch64_include/ | ||
To build static library for ARM64 with MSVC using visual studio solution, *msvc_build* folder have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I read this sentence again, it seems to be missing words. Should it be "must have"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was another rewrite of the readme that somebody submitted a few months ago. I never merged it. Did they rewrite this section?
README.md
Outdated
@@ -184,10 +184,10 @@ For iOS builds, the ``libffi.xcodeproj`` Xcode project is available. | |||
|
|||
Configure has many other options. Use ``configure --help`` to see them all. | |||
|
|||
Once configure has finished, type "make". Note that you must be using | |||
GNU make. You can ftp GNU make from ftp.gnu.org:/pub/gnu/make . | |||
Once configure has finished, type *"make"*. Note that you must be using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe make
or make, but probably not "make". What makes more sense?