From: andrea rossato <andrea.rossato-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: error on building the windows installer
Date: Thu, 08 Nov 2012 19:24:50 +0100 [thread overview]
Message-ID: <87fw4kx899.fsf@eeepc.nowhere.net> (raw)
In-Reply-To: <20121108171447.GD94362-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org> (John MacFarlane's message of "Thu, 8 Nov 2012 09:14:48 -0800")
John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> In citeproc-hs there also seems to be a bug which shows up when building
>> with the "embed_data_files" flags. I'm going to fix it later this
>> afternoon.
>
> My present thought is that pandoc's 'library' and 'executable' flags
> create too many problems. I'm thinking of getting rid of them, and
> adding an embed_data_files flag to embed the data files into the binary.
> (The added size is fairly insignificant since the binary is already so
> large.) This would allow you to make a relocatable executable, not just
> on Windows but on any system. And it would be fully relocatable --
> copy the binary anywhere and it will work, without the need of
> supporting data files.
>
> This would also solve the problem with man pages noted above, as
> we would no longer need the -library flag.
>
> Anyway, I was going to use citeproc-hs as a model, so let me know what
> the problem was!
The problem was just me: I didn't check if the code compiled with the
"embed_data_files" flag before releasing 0.3.6.
The bug was due to the fact that when moving to hexpat I started using
lazy bytestrings for reading files, while embed-file uses strict
bytestrings, hence a type error -- easily fixed.
Andrea
next prev parent reply other threads:[~2012-11-08 18:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 23:43 Cesar Romani
2012-11-05 2:30 ` John MacFarlane
[not found] ` <20121105023034.GB15169-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2012-11-06 15:11 ` Cesar Romani
2012-11-06 16:11 ` John MacFarlane
[not found] ` <20121106161118.GB50342-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2012-11-07 2:02 ` Cesar Romani
2012-11-07 17:10 ` John MacFarlane
[not found] ` <20121107171059.GA66573-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2012-11-07 19:40 ` Cesar Romani
2012-11-07 19:48 ` John MacFarlane
[not found] ` <20121107194845.GA21903-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2012-11-08 11:39 ` andrea rossato
[not found] ` <87sj8kxr1f.fsf-46C4ZU908FJ9y4XLxYaG4V6hYfS7NtTn@public.gmane.org>
2012-11-08 17:14 ` John MacFarlane
[not found] ` <20121108171447.GD94362-9Rnp8PDaXcZ2EAH53EmH34tHsfhOvSUSZkel5v8DVj8@public.gmane.org>
2012-11-08 18:24 ` andrea rossato [this message]
[not found] ` <87fw4kx899.fsf-46C4ZU908FJ9y4XLxYaG4V6hYfS7NtTn@public.gmane.org>
2012-12-22 15:02 ` Cesar Romani
2012-12-30 3:34 ` John MacFarlane
[not found] ` <20121230033457.GA17954-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-01-02 20:41 ` Cesar Romani
2013-01-02 23:55 ` John MacFarlane
[not found] ` <20130102235536.GA19032-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2013-01-10 14:48 ` Huashan Chen
[not found] ` <CAC1OX+AwPWip5GxUSg-8W2ST4Rcn6Vyk3aH+7+tgeZipZwm29g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-10 17:26 ` John MacFarlane
[not found] ` <20130110172629.GB67105-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-01-11 13:39 ` Huashan Chen
[not found] ` <CAC1OX+CctCg1gMy+uURs8rQcs7YLU8L5uzr77g+ebUpmewg2eQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-11 15:43 ` John MacFarlane
[not found] ` <20130111154356.GA73415-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-01-12 16:45 ` Huashan Chen
[not found] ` <CAC1OX+BO-n6HRxdiJfkYTD6GFmTqcD5be5FaxmAUq4+FXwszvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-12 17:42 ` John MacFarlane
[not found] ` <20130112174216.GA93250-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-01-13 0:47 ` Huashan Chen
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=87fw4kx899.fsf@eeepc.nowhere.net \
--to=andrea.rossato-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).