From: sww1235 <sww1235@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Freecad: Update to 0.19.1
Date: Wed, 17 Mar 2021 00:33:12 +0100 [thread overview]
Message-ID: <20210316233312.0lciT4ltoQMiJWrLcKIieZN-Yx18oe_qinCv1ozbCWs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29466@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
New comment by sww1235 on void-packages repository
https://github.com/void-linux/void-packages/pull/29466#issuecomment-800679376
Comment:
The python 2 patch is needed, as otherwise cmake tries to look for python 2.7. not quite sure why, but it didn't build without it
I can add the comment to the vtk9 patch if people would like. Felt it was pretty self explanatory.
Where is patch 152 from? Your own build? Fine with including it, but it didn't seem to be needed to build.
I had been using these same exact patches on my branch of void-packages to build the master branch of freecad and had been using it with no problems.
next prev parent reply other threads:[~2021-03-16 23:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 0:21 [PR PATCH] " sww1235
2021-03-15 0:32 ` ericonr
2021-03-15 22:44 ` sww1235
2021-03-16 1:57 ` [PR PATCH] [Updated] " sww1235
2021-03-16 2:00 ` sww1235
2021-03-16 19:05 ` yopito
2021-03-16 19:06 ` yopito
2021-03-16 20:27 ` karl-nilsson
2021-03-16 20:57 ` sww1235
2021-03-16 21:03 ` ericonr
2021-03-16 21:16 ` karl-nilsson
2021-03-16 21:43 ` yopito
2021-03-16 22:37 ` yopito
2021-03-16 23:28 ` sww1235
2021-03-16 23:29 ` sww1235
2021-03-16 23:33 ` sww1235 [this message]
2021-03-17 19:07 ` yopito
2021-03-17 20:43 ` yopito
2021-03-18 1:58 ` sww1235
2021-03-18 19:31 ` yopito
2021-03-20 3:10 ` [PR PATCH] [Closed]: " sww1235
2021-03-20 3:11 ` sww1235
2021-03-19 7:02 [PR PATCH] [WIP] freecad: update " yopito
2021-03-21 17:55 ` yopito
2021-03-22 4:15 ` sww1235
2021-03-25 4:19 ` ericonr
2021-03-25 6:44 ` yopito
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=20210316233312.0lciT4ltoQMiJWrLcKIieZN-Yx18oe_qinCv1ozbCWs@z \
--to=sww1235@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).