From: yopito <yopito@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] occt: update to 7.6.2
Date: Tue, 26 Jul 2022 05:40:56 +0200 [thread overview]
Message-ID: <20220726034056.BZ_Dpbdq92w-U60iQU_WwTH99C8jVEKapQsjr5TqVVc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36356@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
New comment by yopito on void-packages repository
https://github.com/void-linux/void-packages/pull/36356#issuecomment-1194959837
Comment:
regarding FreeCAD 0.20 (only): I have some WIP on it, here some points about it:
* help is not generated anymore from source by available (only) from online: see my review of your freecad/template
* `freecad/patches/010-salomesmesh-execinfo.patch` is uneeded anymore
* I've also update libspnav to 1.0 on my side, so additional patch for freecad is needed: could you add these into your commits ?
* libspnav : update to 1.0: https://gist.github.com/yopito/2757c1a501e2772143814b4a3553cbea
* freecad: : fix PATH_MAX on musl libc : https://gist.github.com/yopito/fd25b30edcbc762babd9069641a9b86e
* another fix:
* freecad: : fix build (stderr resource is readonly): https://gist.github.com/yopito/3ac7d4c8fee646171ca900ff17452567
* I have some SIGSEGV on running FreeCAD (x86_64 musl) when it's using Coin/pivy and shiboken2/pyside2 in 5.15.5 (in WIP) : don't know yet if related to shiboken2/pyside2 in 5.15.5 : see https://github.com/coin3d/pivy/issues/98
=> could you run at least `FreeCAD -t MeshTestsApp` to see if you have the same trouble ?
next prev parent reply other threads:[~2022-07-26 3:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 4:42 [PR PATCH] [WIP] occt: update to 7.6.1 karl-nilsson
2022-03-26 15:07 ` [PR PATCH] [Updated] " karl-nilsson
2022-03-26 15:26 ` karl-nilsson
2022-03-28 19:00 ` Piraty
2022-05-01 20:20 ` [PR PATCH] [Updated] " karl-nilsson
2022-05-01 20:24 ` karl-nilsson
2022-05-01 20:24 ` karl-nilsson
2022-05-02 14:17 ` karl-nilsson
2022-05-02 14:18 ` karl-nilsson
2022-05-02 14:51 ` [WIP] occt: update to 7.6.2 karl-nilsson
2022-07-04 11:21 ` luzpaz
2022-07-24 1:21 ` [PR PATCH] [Updated] " karl-nilsson
2022-07-24 1:40 ` karl-nilsson
2022-07-24 3:02 ` karl-nilsson
2022-07-24 4:11 ` luzpaz
2022-07-25 1:10 ` [PR PATCH] [Updated] " karl-nilsson
2022-07-25 1:31 ` karl-nilsson
2022-07-25 3:02 ` karl-nilsson
2022-07-25 3:38 ` karl-nilsson
2022-07-25 13:16 ` [PR PATCH] [Updated] " karl-nilsson
2022-07-26 3:39 ` [PR REVIEW] " yopito
2022-07-26 3:40 ` yopito [this message]
2022-08-12 9:12 ` yopito
2022-08-12 14:24 ` luzpaz
2022-08-12 14:25 ` luzpaz
2022-08-22 11:48 ` yopito
2022-08-22 11:57 ` yopito
2022-08-22 13:59 ` karl-nilsson
2022-08-23 13:29 ` yopito
2022-09-27 19:34 ` enderger
2022-10-01 16:02 ` [PR PATCH] [Updated] " karl-nilsson
2022-10-01 21:16 ` karl-nilsson
2022-10-01 21:18 ` karl-nilsson
2022-10-01 21:35 ` karl-nilsson
2022-10-01 21:50 ` karl-nilsson
2022-10-02 2:13 ` karl-nilsson
2022-10-02 2:31 ` karl-nilsson
2022-12-19 0:31 ` Piraty
2023-01-20 3:23 ` luzpaz
2023-04-21 1:52 ` github-actions
2023-04-24 22:34 ` luzpaz
2023-04-30 19:32 ` Piraty
2023-04-30 19:32 ` [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=20220726034056.BZ_Dpbdq92w-U60iQU_WwTH99C8jVEKapQsjr5TqVVc@z \
--to=yopito@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).