From: kedodrill <kedodrill@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: TrenchBroom-2021.1
Date: Fri, 13 May 2022 21:47:48 +0200 [thread overview]
Message-ID: <20220513194748.eJnUv1XB87PCqgjDDg0pNGdN3GqTrPp5YP5v058lWgY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33354@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]
There's a closed pull request on the void-packages repository
New package: TrenchBroom-2021.1
https://github.com/void-linux/void-packages/pull/33354
Description:
<!-- Mark items with [x] where applicable -->
https://github.com/TrenchBroom/TrenchBroom
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
- [x] I built this PR locally for my native architecture, x86_64
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] x86_64-musl - success, added patch
- [x] armv7l - failed, see [here](https://github.com/TrenchBroom/TrenchBroom/issues/3651) afaik ARM is not supported because of this, but I'm not 100% sure. The error in the builder makes me think a lib is missing, but if that issue is correct - even if we get it working, I don't think the program loads correctly because of shader issues.
- [x] i686 - success
- [x] i686 (crossbuild) - failed, `CMake Error: AUTOMOC for target common: Test run of "moc" executable "/usr/i686-pc-linux-gnu/usr/lib/qt5/bin/moc" failed.` any help on this would be appreciated, but I'm not sure how required crossbuilding is for this.
See readme, TB will crash on wayland if `QT_QPA_PLATFORM` is set to `wayland`.
Closes https://github.com/void-linux/void-packages/issues/31317
prev parent reply other threads:[~2022-05-13 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 20:41 [PR PATCH] " kedodrill
2021-10-29 17:53 ` [PR PATCH] [Updated] [WIP] " kedodrill
2021-10-29 18:00 ` kedodrill
2021-10-29 22:30 ` kedodrill
2022-05-13 19:47 ` kedodrill
2022-05-13 19:47 ` kedodrill [this message]
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=20220513194748.eJnUv1XB87PCqgjDDg0pNGdN3GqTrPp5YP5v058lWgY@z \
--to=kedodrill@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).