From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Pavel Begunkov <asml.silence@gmail.com>,
Christian Mazakas <christian.mazakas@gmail.com>,
Gilang Fachrezy <gilang4321@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
VNLX Kernel Department <kernel@vnlx.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: [RFC PATCH v1 liburing 2/2] README: Explain about FFI support
Date: Sat, 14 Jan 2023 16:55:23 +0700 [thread overview]
Message-ID: <20230114095523.460879-3-ammar.faizi@intel.com> (raw)
In-Reply-To: <20230114095523.460879-1-ammar.faizi@intel.com>
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Tell people that they should use the FFI variants when they can't use
'static inline' functions defined in liburing.h.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
README | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/README b/README
index 4dd59f6..7babb3b 100644
--- a/README
+++ b/README
@@ -71,6 +71,25 @@ Building liburing
See './configure --help' for more information about build config options.
+FFI support
+-----------
+
+By default, the build results in 4 lib files:
+
+ 2 shared libs:
+
+ liburing.so
+ liburing-ffi.so
+
+ 2 static libs:
+
+ liburing.a
+ liburing-ffi.a
+
+For languages and applications that can't use 'static inline' functions in
+liburing.h should use the FFI variants.
+
+
License
-------
--
Ammar Faizi
next prev parent reply other threads:[~2023-01-14 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 9:55 [RFC PATCH liburing v1 0/2] Explain how to build liburing and FFI support Ammar Faizi
2023-01-14 9:55 ` [RFC PATCH v1 liburing 1/2] README: Explain how to build liburing Ammar Faizi
2023-01-14 9:55 ` Ammar Faizi [this message]
2023-01-14 17:19 ` [RFC PATCH v1 liburing 2/2] README: Explain about FFI support Jens Axboe
[not found] ` <CAHf7xWs1hWvqb61tpBq63CLFvSk=kfAn_nq_2t2gf7O8V9qZ6A@mail.gmail.com>
2023-01-15 18:18 ` Jens Axboe
2023-01-16 4:18 ` Christian Mazakas
2023-01-16 13:44 ` Jens Axboe
2023-01-16 13:54 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230114095523.460879-3-ammar.faizi@intel.com \
--to=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=christian.mazakas@gmail.com \
--cc=gilang4321@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=kernel@vnlx.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox