Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PrusaSlicer: update to 2.5.0. #41548

Closed
wants to merge 2 commits into from
Closed

PrusaSlicer: update to 2.5.0. #41548

wants to merge 2 commits into from

Conversation

sinetek
Copy link

@sinetek sinetek commented Jan 9, 2023

Bump the version for PrusaSlicer to 2.5.0.
Note that this does not require the new occt version. When the version for occt is bumped, we can enable the new STEP file support. Otherwise just keep it as it was.

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-glibc

srcpkgs/PrusaSlicer/patches/cereal-is-header-only.patch Outdated Show resolved Hide resolved
srcpkgs/PrusaSlicer/template Outdated Show resolved Hide resolved
srcpkgs/PrusaSlicer/patches/boost-1.81.patch Outdated Show resolved Hide resolved
@sinetek sinetek changed the title PrusaSlicer: update to 4.5.0. PrusaSlicer: update to 2.5.0. Jan 14, 2023
@sinetek
Copy link
Author

sinetek commented Jan 15, 2023

Hi, please see changes, I think it is ready for merge.

  • compiled on musl
  • fixed the revision number
  • fixed the patching 'cereal', now it applies correctly.
  • corrected the title, and commit title version number.

@sinetek sinetek requested review from a user and sgn and removed request for a user and sgn January 15, 2023 21:15
@sinetek
Copy link
Author

sinetek commented Jan 30, 2023

bump.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Squash your commits together; retain the explanation regarding prusa-slicer.desktop.

The other problem I see here is that you want to merge changes from your master branch, not the feature-related like you are supposed to.

From CONTRIBUTING.md:

Using the `master` branch of your fork for contributing is also strongly discouraged.
It can cause many issues with updating your pull request (also called a PR), and having multiple PRs open at once.

build_style=cmake
build_helper="qemu cmake-wxWidgets-gtk3"
# Pre-Compiled Headers seems to be slower
configure_args="-DSLIC3R_WX_STABLE=1 -DSLIC3R_FHS=1 -DSLIC3R_GTK=3
-DSLIC3R_ENC_CHECK=0 -DUSE_BLOSC=ON -DUSE_EXR=ON -DSLIC3R_PCH=OFF"
-DSLIC3R_ENC_CHECK=0 -DUSE_BLOSC=ON -DUSE_EXR=ON -DSLIC3R_PCH=OFF -DSLIC3R_ENABLE_FORMAT_STEP="
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
-DSLIC3R_ENC_CHECK=0 -DUSE_BLOSC=ON -DUSE_EXR=ON -DSLIC3R_PCH=OFF -DSLIC3R_ENABLE_FORMAT_STEP="
-DSLIC3R_ENC_CHECK=0 -DUSE_BLOSC=ON -DUSE_EXR=ON -DSLIC3R_PCH=OFF -DSLIC3R_ENABLE_FORMAT_STEP=OFF"

Why not just set it to OFF? Cmake triggers on booleans, not the contents of the variable:

if (SLIC3R_ENABLE_FORMAT_STEP)
    add_subdirectory(occt_wrapper)
endif ()

generate_export_header(OCCTWrapper)

-find_package(OpenCASCADE 7.6.2 REQUIRED)
+find_package(OpenCASCADE 7.4.0...7.999.999 REQUIRED)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
+find_package(OpenCASCADE 7.4.0...7.999.999 REQUIRED)
+find_package(OpenCASCADE REQUIRED)

If I recall it right, omitting the version should also do the trick.

@@ -0,0 +1,81 @@
From 408e56f0390f20aaf793e0aa0c70c4d9544401d4 Mon Sep 17 00:00:00 2001
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
From 408e56f0390f20aaf793e0aa0c70c4d9544401d4 Mon Sep 17 00:00:00 2001
https://github.com/prusa3d/Prusaslicer/commit/408e56f0390f20aaf793e0aa0c70c4d9544401d4
From 408e56f0390f20aaf793e0aa0c70c4d9544401d4 Mon Sep 17 00:00:00 2001

@github-actions
Copy link

github-actions bot commented May 3, 2023

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

@github-actions github-actions bot added the Stale label May 3, 2023
@github-actions github-actions bot closed this May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants