public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: brainchild <ericlevy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: build customizability
Date: Fri, 1 May 2020 06:57:50 -0700 (PDT)	[thread overview]
Message-ID: <43e8ce91-0738-4477-bcf5-e826219d9b1d@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 855 bytes --]


If someone wished to ship a functional executable of Pandoc in the 
distribution of a larger application, what possibility, if any, currently 
exists for building such an executable that only provides selected features 
of the full application but is significantly smaller in distribution 
footprint? In other words, what possibility is available, separate from any 
generic compiler settings, to customize a build for reduced executable size?

-- 
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/43e8ce91-0738-4477-bcf5-e826219d9b1d%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1191 bytes --]

             reply	other threads:[~2020-05-01 13:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 13:57 brainchild [this message]
     [not found] ` <43e8ce91-0738-4477-bcf5-e826219d9b1d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-01 15:51   ` John MacFarlane
     [not found]     ` <m2wo5vy7pz.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-05-03  8:05       ` brainchild
     [not found]         ` <a9b39338-0830-45dc-bf30-59d8de61278b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-03 12:39           ` Albert Krewinkel
     [not found]             ` <87wo5tgpkn.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-05-03 12:55               ` brainchild
     [not found]                 ` <459f63cf-31b3-48a4-adfe-21d5f23f9d22-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-03 13:39                   ` Ivan Lazar Miljenovic
     [not found]                     ` <CA+u6gbwbuU9QhDFygzHh259Pa99qCTNBAq6-Jym6z24hhCF=PQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-03 14:05                       ` BPJ
2020-05-03 15:07                   ` Albert Krewinkel
2020-05-04  6:45   ` brainchild
     [not found]     ` <f9fd9cfe-e03f-45d3-bcb5-07267c28e565-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-04 14:47       ` Daniel Staal
     [not found]         ` <75f238b6-2ae0-2e73-66c9-54245b7cd655-Jdbf3xiKgS8@public.gmane.org>
2020-05-05  2:11           ` brainchild
2020-05-05  8:39           ` Colored text R. Wils
     [not found]             ` <CAJPsUMeBTr2BcSL8V8mQuh=50LDx+z8+547MUcMzZYqahF9CAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-05-05  8:42               ` brainchild
2020-05-04  8:36   ` build customizability brainchild

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=43e8ce91-0738-4477-bcf5-e826219d9b1d@googlegroups.com \
    --to=ericlevy-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).