From: andkem <andkem@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: siril: update to 0.99.4.
Date: Sat, 05 Sep 2020 17:13:15 +0200 [thread overview]
Message-ID: <20200905151315.ebIH8qfrn23nou2Rn8NXxL0QDDH4wgm7pwnC4dnDHQ0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24678@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
New comment by andkem on void-packages repository
https://github.com/void-linux/void-packages/pull/24678#issuecomment-687607213
Comment:
They first released 0.99.4 as a beta test for version 1.0.0, but then they decided that it was stable enough and released 0.99.4 as a proper release. (Or rather, it is still a beta version and initial release was for Windows, Mac and Debian for testing, but has then been expanded to more platforms which makes me think this should be all right.)
They bundle the librtprocess code with Siril and build it automatically if it isn't found when you're not cross-compiling. It lives in a subdirectory and uses cmake to build.
I'll have a look at creating a proper package for librtprocess, which I think is preferable to patching the Siril build process to allow building it for cross compilation.
next prev parent reply other threads:[~2020-09-05 15:13 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 1:02 [PR PATCH] " andkem
2020-09-05 1:04 ` [PR PATCH] [Updated] " andkem
2020-09-05 1:06 ` andkem
2020-09-05 1:09 ` andkem
2020-09-05 1:45 ` andkem
2020-09-05 1:59 ` ericonr
2020-09-05 12:53 ` andkem
2020-09-05 14:17 ` [PR PATCH] [Updated] " andkem
2020-09-05 15:12 ` andkem
2020-09-05 15:13 ` andkem [this message]
2020-09-05 15:15 ` andkem
2020-09-05 16:24 ` andkem
2020-09-05 19:38 ` [PR PATCH] [Updated] " andkem
2020-09-05 20:45 ` andkem
2020-09-23 21:25 ` andkem
2020-09-23 21:26 ` siril: update to 0.99.6 andkem
2021-02-14 16:23 ` [PR PATCH] [Updated] " andkem
2021-02-14 17:14 ` [PR PATCH] [Updated] siril: update to 0.99.8.1 andkem
2021-02-14 17:22 ` andkem
2021-02-14 17:53 ` [PR PATCH] [Updated] " andkem
2021-02-14 18:11 ` andkem
2021-02-14 19:10 ` andkem
2021-02-14 23:15 ` [PR REVIEW] " ericonr
2021-02-14 23:15 ` ericonr
2021-02-14 23:15 ` ericonr
2021-02-15 18:07 ` [PR PATCH] [Updated] " andkem
2021-02-15 18:26 ` [PR REVIEW] " andkem
2021-02-15 18:26 ` andkem
2021-02-15 18:26 ` andkem
2021-05-27 18:47 ` [PR PATCH] [Updated] " andkem
2021-05-27 18:51 ` andkem
2021-05-27 18:53 ` andkem
2021-06-17 22:10 ` [PR PATCH] [Updated] " andkem
2021-06-17 22:10 ` siril: update to 0.99.10 andkem
2022-03-10 23:19 ` [PR PATCH] [Updated] " andkem
2022-03-10 23:21 ` siril: update to 1.0.0 andkem
2022-03-10 23:23 ` [PR PATCH] [Updated] " andkem
2022-03-10 23:42 ` andkem
2022-05-17 21:57 ` andkem
2022-05-17 22:11 ` siril: update to 1.0.2 andkem
2022-06-04 22:07 ` [PR PATCH] [Updated] " andkem
2022-06-10 13:14 ` [PR PATCH] [Closed]: " leahneukirchen
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=20200905151315.ebIH8qfrn23nou2Rn8NXxL0QDDH4wgm7pwnC4dnDHQ0@z \
--to=andkem@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).