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 09:31:11 -0700	[thread overview]
Message-ID: <2242AE1C-C331-4335-8764-5D16C0F925D9@gmail.com> (raw)
In-Reply-To: <76e8af61-df27-472a-986d-030a883998fan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>



> On Mar 15, 2023, at 9:11 AM, Jim Pryor <jim.pryor.nyu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> I used to follow the instructions at <https://pandoc.org/installing.html#custom-cabal-method> to build pandoc with the cabal configure `--flags="embed_data_files lua53"`.
> 
> Since `git pull`ing to the pandoc 3.* source tree, this no longer builds an executable. I see from the Pandoc 3.0 announcement on this list that the packaging has split in some ways.
> 
> Is it still possible to build all the components with custom cabal configure flags? How do I go about it? Can I just cd to the `pandoc-cli` subdirectory and do the following there:
> 
> ```
> cabal update
> cabal install --only-dependencies
> 
> cabal configure --prefix=/usr/local --flags="embed_data_files lua53"
> 
> cabal build
> 
> ./dist-newstyle/build/x86_64-osx/ghc-*/pandoc-*/x/pandoc/build/pandoc/pandoc --version
> 
> ```


Something like this should work, but there have been changes in both pandoc and cabal since the instructions were composed, so they may need some adjusting. Try it?

You'll want to add lua and server to your flags if you want the executable to have Lua and server support, respectively.  lua53 is no longer available, sorry.

> 
> Or do I have to first run those steps in the top-level directory, then do `cabal install`, then repeat them in the `pandoc-cli` subdirectory? When I try to only do the steps in the `pandoc-cli` subdirectory, it seems like a binary version of the main `pandoc` library is being downloaded, rather than one built using my custom configure flags.

cabal never downloads binaries, only source. If it's happening quickly, it could be because your global cabal store already contains a built version of the library.


-- 
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/2242AE1C-C331-4335-8764-5D16C0F925D9%40gmail.com.


  parent reply	other threads:[~2023-03-15 16:31 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 [this message]
     [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
     [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=2242AE1C-C331-4335-8764-5D16C0F925D9@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).