public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Custom cabal builds for pandoc 3.*?
Date: Wed, 15 Mar 2023 15:37:15 -0700	[thread overview]
Message-ID: <EFF25C3F-EBD2-48A2-8C3B-4C58E0EE8EE0@gmail.com> (raw)
In-Reply-To: <acdc69b2-c368-45e8-9154-23c280d09cdbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]



> On Mar 15, 2023, at 10:43 AM, Jim Pryor <jim.pryor.nyu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Thanks for the quick reply. It looks like I can just cd into the `pandoc-cli` subdirectory and do the configure and build from there. Doesn't seem to be necessary to first do the build (with or without install) from the toplevel directory. Not sure how to confirm that the library was built with the `embed_data_files` option though

You could try

strings /path/to/pandoc | grep ‘\$title\$’

which should give you output if the templates are baked in to the binary.


-- 
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/EFF25C3F-EBD2-48A2-8C3B-4C58E0EE8EE0%40gmail.com.

[-- Attachment #2: Type: text/html, Size: 2270 bytes --]

  parent reply	other threads:[~2023-03-15 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 16:11 Jim Pryor
     [not found] ` <76e8af61-df27-472a-986d-030a883998fan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-15 16:31   ` John MacFarlane
     [not found]     ` <2242AE1C-C331-4335-8764-5D16C0F925D9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-03-15 17:43       ` Jim Pryor
     [not found]         ` <acdc69b2-c368-45e8-9154-23c280d09cdbn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-15 22:37           ` John MacFarlane [this message]
     [not found]             ` <EFF25C3F-EBD2-48A2-8C3B-4C58E0EE8EE0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-03-16  2:34               ` Jim Pryor

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=EFF25C3F-EBD2-48A2-8C3B-4C58E0EE8EE0@gmail.com \
    --to=fiddlosopher-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).