From: jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: command-line pandoc on iOS
Date: Sun, 16 Oct 2022 08:20:27 -0700 (PDT) [thread overview]
Message-ID: <bfa54f4a-eedc-4e8e-8671-1aa9f6c63e1dn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1870 bytes --]
I would like to be able to run pandoc-based document builds on an iPad.
This seems to be possible with the [a-Shell
app](https://holzschu.github.io/a-Shell_iOS/). It provides a Unix-like
shell with LaTeX (additional 1.3GB download), Python, Lua, and many command
line utilities. C and C++ programs can be compiled to WebAssembly on the
device and run there. It is also possible to cross-compile for a-Shell,
using a [customized WASI-SDK](https://github.com/holzschu/wasi-sdk).
[Asterius](https://github.com/tweag/asterius) compiles Haskell to
WebAssembly, and there are a couple of demos that use it to run pandoc in a
webpage, but the WebAssembly files they use offer a simple JavaScript
interface to the Haskell pandoc function: (input, from format, to format)
-> output. I need the full command line interface to run document builds.
It looks possible, but since I've never used Haskell, its build tools, or
WASI-SDK, I'm not sure how to go about this. There's a pre-built Docker
container for Asterius with about 2000 packages from Stockage (I think I
can guess what that is), but I don't know if I can use that, or if I have
to rebuild everything from scratch using the customized WASI-SDK. After
that, I guess I would download the pandoc source and follow the
instructions for building it with cabal, using `ahc-cabal` in place of
`cabal`. But if anything goes wrong with the cabal build, I'll be lost.
Has anyone already done this?
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/bfa54f4a-eedc-4e8e-8671-1aa9f6c63e1dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2226 bytes --]
next reply other threads:[~2022-10-16 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 15:20 jcr [this message]
[not found] ` <bfa54f4a-eedc-4e8e-8671-1aa9f6c63e1dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-16 17:58 ` John MacFarlane
[not found] ` <5346511C-4B5D-42E9-B287-DB005CB4D005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-17 9:15 ` ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <ADB72C63-745E-4D50-9045-E60813FA08EB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-17 14:47 ` John MacFarlane
[not found] ` <8FB22757-A6A4-432C-80F3-E770F0567E89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-07 16:56 ` jcr
[not found] ` <626e5a36-6440-4be0-a5f6-9910f551ffc0n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-07 19:20 ` John MacFarlane
[not found] ` <DE26E142-2E87-469E-809B-8DD59EA9460B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-07 19:22 ` John MacFarlane
[not found] ` <9F9D7B72-C9B2-477C-A48A-2B6EDAC95E3D-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-23 19:14 ` Sébastien Boisgérault
[not found] ` <0afec597-2662-487a-8e2d-6c74c85b3ca5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-28 21:23 ` John MacFarlane
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=bfa54f4a-eedc-4e8e-8671-1aa9f6c63e1dn@googlegroups.com \
--to=ffi.appdev-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).