From: Gottox <Gottox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: PrusaSlicer: update to 2.5.0
Date: Tue, 11 Oct 2022 08:20:56 +0200 [thread overview]
Message-ID: <20221011062056.OXQNEZFcUxWF-cshz8CMFbHJAgJXpfLQDg4HvKYC9Jc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39875@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
New comment by Gottox on void-packages repository
https://github.com/void-linux/void-packages/pull/39875#issuecomment-1274141480
Comment:
The issue with this PR is, that `occt` is pinned to 7.6.2. This will break any update to `occt`. I suggest the following patch to relax this requirements to PrusaSlicer:
```cat patches/cmake-relax-dependency.patch```:
```patch
--- PrusaSlicer-version_2.5.0/src/occt_wrapper/CMakeLists.txt.orig 2022-09-17 11:47:02.398209546 +0200
+++ PrusaSlicer-version_2.5.0/src/occt_wrapper/CMakeLists.txt 2022-09-17 11:47:30.092595307 +0200
@@ -19,7 +19,7 @@ include(GenerateExportHeader)
generate_export_header(OCCTWrapper)
-find_package(OpenCASCADE 7.6.2 REQUIRED)
+find_package(OpenCASCADE 7.6.2...7.999.999 REQUIRED)
set(OCCT_LIBS
TKXDESTEP
```
next prev parent reply other threads:[~2022-10-11 6:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 21:18 [PR PATCH] " hvraven
2022-10-11 6:20 ` Gottox
2022-10-11 6:20 ` Gottox [this message]
2022-10-11 9:07 ` [PR PATCH] [Updated] " hvraven
2022-10-11 9:08 ` hvraven
2022-10-22 17:10 ` sgn
2022-12-22 20:08 ` vincele
2023-03-23 1:53 ` github-actions
2023-04-07 1:49 ` [PR PATCH] [Closed]: " github-actions
2023-01-09 16:16 [PR PATCH] PrusaSlicer: update to 4.5.0 sinetek
2023-01-15 17:13 ` PrusaSlicer: update to 2.5.0 sinetek
2023-01-15 17:13 ` sinetek
2023-01-30 13:29 ` sinetek
2023-05-03 1:51 ` github-actions
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=20221011062056.OXQNEZFcUxWF-cshz8CMFbHJAgJXpfLQDg4HvKYC9Jc@z \
--to=gottox@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).