From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Albert Krewinkel
<albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: My build executable file very larger then release
Date: Tue, 31 May 2022 13:16:16 -0700 [thread overview]
Message-ID: <m25yllzcdr.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <871qwa6x1n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
It could be that the -split-sections option is responsible
for some of the shrinking.
Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> writes:
> A jeep <ajeep8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> I'm not familiar with Haskell.
>>
>> In my utuntu 20.04, I `stack install pandoc pandoc-crossref`, the
>> result exec files are very larger then official release:
>>
>> [...]
>>
>> How can I shrink the exec files to pandoc official release file size?
>
> The main trick is to use `strip`, a tool to remove debug symbols and
> other data that's not required.
>
> See also the script linux/make_artifacts.sh, which is used to generate
> the official release binaries.
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
> --
> 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/871qwa6x1n.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2022-05-31 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 5:18 A jeep
[not found] ` <5e412d02-44fd-4ce5-947e-9872cb918c1cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-05-31 6:18 ` Albert Krewinkel
[not found] ` <871qwa6x1n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-31 20:16 ` John MacFarlane [this message]
[not found] ` <m25yllzcdr.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-01 7:05 ` A jeep
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=m25yllzcdr.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=albert+pandoc-9EawChwDxG8hFhg+JK9F0w@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).