summaryrefslogtreecommitdiff
path: root/share/man/man1/aarch64-linux-android-dlltool.1
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man1/aarch64-linux-android-dlltool.1')
-rw-r--r--share/man/man1/aarch64-linux-android-dlltool.143
1 files changed, 26 insertions, 17 deletions
diff --git a/share/man/man1/aarch64-linux-android-dlltool.1 b/share/man/man1/aarch64-linux-android-dlltool.1
index 303413f..7a8a98e 100644
--- a/share/man/man1/aarch64-linux-android-dlltool.1
+++ b/share/man/man1/aarch64-linux-android-dlltool.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -38,6 +38,8 @@
. ds PI \(*p
. ds L" ``
. ds R" ''
+. ds C`
+. ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
-.ie \nF \{\
-. de IX
-. tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
..
-. nr % 0
-. rr F
-.\}
-.el \{\
-. de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+. if \nF \{
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
..
+. if !\nF==2 \{
+. nr % 0
+. nr F 2
+. \}
+. \}
.\}
+.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
@@ -124,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "DLLTOOL 1"
-.TH DLLTOOL 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH DLLTOOL 1 "2014-08-29" "binutils-2.24.0" "GNU Development Tools"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -168,19 +177,19 @@ has been specified it creates a def file. Any or all of the \fB\-e\fR,
\&\fB\-l\fR and \fB\-z\fR options can be present in one invocation of
dlltool.
.PP
-When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
+When creating a \s-1DLL,\s0 along with the source for the \s-1DLL,\s0 it is necessary
to have three other files. \fBdlltool\fR can help with the creation of
these files.
.PP
The first file is a \fI.def\fR file which specifies which functions are
-exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on. This
+exported from the \s-1DLL,\s0 which functions the \s-1DLL\s0 imports, and so on. This
is a text file and can be created by hand, or \fBdlltool\fR can be used
to create it using the \fB\-z\fR option. In this case \fBdlltool\fR
will scan the object files specified on its command line looking for
those functions which have been specially marked as being exported and
put entries for them in the \fI.def\fR file it creates.
.PP
-In order to mark a function as being exported from a \s-1DLL\s0, it needs to
+In order to mark a function as being exported from a \s-1DLL,\s0 it needs to
have an \fB\-export:<name_of_function>\fR entry in the \fB.drectve\fR
section of the object file. This can be done in C by using the
\&\fIasm()\fR operator:
@@ -199,7 +208,7 @@ binary file and it can be created by giving the \fB\-e\fR option to
\&\fBdlltool\fR when it is creating or reading in a \fI.def\fR file.
.PP
The third file needed for \s-1DLL\s0 creation is the library file that programs
-will link with in order to access the functions in the \s-1DLL\s0 (an `import
+will link with in order to access the functions in the \s-1DLL \s0(an `import
library'). This file can be created by giving the \fB\-l\fR option to
dlltool when it is creating or reading in a \fI.def\fR file.
.PP
@@ -338,7 +347,7 @@ double quotes.
Specifies the name to be stored in the \fI.def\fR file as the name of
the \s-1DLL\s0 when the \fB\-e\fR option is used. If this option is not
present, then the filename given to the \fB\-e\fR option will be
-used as the name of the \s-1DLL\s0.
+used as the name of the \s-1DLL.\s0
.IP "\fB\-m\fR \fImachine\fR" 4
.IX Item "-m machine"
.PD 0
@@ -392,7 +401,7 @@ party DLLs that were built with MS-Windows tools.
Specifies that when \fBdlltool\fR is creating the exports file it
should not append the string \fB@ <number>\fR. These numbers are
called ordinal numbers and they represent another way of accessing the
-function in a \s-1DLL\s0, other than by name.
+function in a \s-1DLL,\s0 other than by name.
.IP "\fB\-A\fR" 4
.IX Item "-A"
.PD 0
@@ -451,7 +460,7 @@ actually an import library. See also \fB\-\-identify\-strict\fR.
.IX Item "--identify-strict"
Modifies the behavior of the \fB\-\-identify\fR option, such
that an error is reported if \fIfilename\fR is associated with
-more than one \s-1DLL\s0.
+more than one \s-1DLL.\s0
.IP "\fB\-i\fR" 4
.IX Item "-i"
.PD 0