From: joey-commits <joey-commits@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: new package: espeak-ng-1.50
Date: Wed, 16 Dec 2020 20:13:53 +0100 [thread overview]
Message-ID: <20201216191353.-hp9gef-qvF3-OIguFFPC-PfZrbwae5JSqPnM7DkWKY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27193@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
New comment by joey-commits on void-packages repository
https://github.com/void-linux/void-packages/pull/27193#issuecomment-746856482
Comment:
I was looking at the data built by the binaries and it doesn't seem to be archetecture specific. I need to look at a bit more to be sure. I am wondering if I could make a nocross package to build the data files and then pull it in for the real espeak-ng package with hostmakedepends. Then it could be coppied to the build directory before the build and the Makefile would detect that the voice dictionaries are already built.
next prev parent reply other threads:[~2020-12-16 19:13 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 8:34 [PR PATCH] " joey-commits
2020-12-16 9:04 ` [PR PATCH] [Updated] " joey-commits
2020-12-16 9:42 ` joey-commits
2020-12-16 16:13 ` joey-commits
2020-12-16 16:46 ` joey-commits
2020-12-16 17:12 ` ericonr
2020-12-16 17:15 ` ericonr
2020-12-16 17:52 ` [PR PATCH] [Updated] " joey-commits
2020-12-16 18:12 ` joey-commits
2020-12-16 19:13 ` joey-commits [this message]
2020-12-16 19:30 ` ericonr
2020-12-16 21:04 ` [PR PATCH] [Updated] " joey-commits
2020-12-16 21:38 ` joey-commits
2020-12-16 21:48 ` joey-commits
2020-12-16 21:59 ` joey-commits
2020-12-17 6:45 ` joey-commits
2020-12-17 14:44 ` [PR REVIEW] " Piraty
2020-12-17 14:45 ` Piraty
2020-12-17 14:55 ` [PR PATCH] [Updated] " joey-commits
2020-12-17 15:05 ` [PR REVIEW] " ericonr
2020-12-17 15:15 ` joey-commits
2020-12-17 15:21 ` joey-commits
2020-12-17 15:31 ` ericonr
2020-12-17 15:35 ` joey-commits
2020-12-17 15:37 ` joey-commits
2020-12-17 15:48 ` [PR PATCH] [Updated] " joey-commits
2020-12-17 15:53 ` ericonr
2020-12-17 15:53 ` ericonr
2020-12-17 15:53 ` ericonr
2020-12-17 15:54 ` [PR PATCH] [Updated] " joey-commits
2020-12-17 16:10 ` joey-commits
2020-12-17 16:48 ` joey-commits
2020-12-17 16:54 ` joey-commits
2020-12-17 21:30 ` Piraty
2020-12-17 21:32 ` Piraty
2020-12-18 7:55 ` [PR PATCH] [Updated] " joey-commits
2020-12-18 9:19 ` joey-commits
2020-12-18 14:34 ` joey-commits
2020-12-18 14:46 ` joey-commits
2020-12-18 20:06 ` ericonr
2020-12-18 20:17 ` joey-commits
2020-12-18 22:04 ` [PR PATCH] [Updated] " joey-commits
2020-12-18 23:47 ` joey-commits
2020-12-19 3:02 ` ericonr
2020-12-19 3:08 ` ericonr
2020-12-19 3:20 ` joey-commits
2020-12-19 3:23 ` joey-commits
2020-12-19 3:25 ` joey-commits
2020-12-19 3:47 ` ericonr
2020-12-19 21:36 ` CMB
2020-12-19 21:57 ` CMB
2020-12-19 22:27 ` ericonr
2020-12-20 19:30 ` [PR PATCH] [Closed]: " Piraty
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=20201216191353.-hp9gef-qvF3-OIguFFPC-PfZrbwae5JSqPnM7DkWKY@z \
--to=joey-commits@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).