OrcaSlicer compiling thread

[SoftFever]

Some people have difficulties building Orca Slicer. This is the thread to discuss such issues.

On Windows:

• Make sure you have installed Strawberry Perl
• Call build_release_vs2022.bat from x64 Native Tools Command Prompt for VS 2022

build_release_vs2022.bat accepts two parameters: deps and slicer. It will build both deps and studio by default if no parameter is provided.

If you have issues compiling OrcaSlicer, please make sure that all dependencies are compiled successfully.
Steps:

1. Delete the build folder: deps/build
2. call build_release_vs2022.bat deps from x64 Native Tools Command Prompt for VS 2022

Note If you want to debug Orca Slicer, you can set the build type to RelWithDebInfo. The debug build type is not maintained, so you might run into errors if you try to build it.

[fr3ak2402]

@SoftFever

I have also tried this and leads to the same error

[SoftFever]

Without looking at the whole log file I have no idea why you can't build OCCT.

But you can use my prebuilt binaries of the deps.

Yes I have that selected in VS too as it is not selected by default, that had installed afterwards because that is what I noticed when I first tried it.

I also downloaded the deps from the CI/CD and couldn't compile that either, I already had those too....

https://github.com/SoftFever/FileSharing/releases/download/OrcaSlicer_deps_Mar/OrcaSlicer_dep_05May2023.zip I had downloaded and tried these but without success.

To use the deps, you will need to clone OrcaSlicer to this location.
D:\a\OrcaSlicer\OrcaSlicer

Then unzip the deps binaries to this location: D:\a\OrcaSlicer\OrcaSlicer\deps\build\OrcaSlicer_dep
You can ref to the CICD build log for more details. https://github.com/SoftFever/OrcaSlicer/actions/runs/5378379616/jobs/9758096469

[fr3ak2402]

Okay... also C:\a\OrcaSlicer\OrcaSlicer\deps\build\OrcaSlicer_dep ?

I can also provide you with the entire log if it helps you.... but let's first try the idea with the Deps...

[fr3ak2402]

So I tried this out, so if I create a USB stick with a drive letter D, building works without any problems.

But when I try to do it on C:, at some point it looks for a hard disk with a drive letter D:... Is it possible to change this to the drive letter C:?

[SoftFever]

Yes it's possible.
You can use subst command to create D drive from a folder.
subst D: path-orcaslicer-folder

[fr3ak2402]

Yes, but that doesn't help me, because unfortunately I have 2 Windows systems installed on my system and I boot them via the boot manager when I boot up. Unfortunately, the other system already has a D drive, which I cannot redefine...

Therefore, I actually need this without a D drive, so that it can only be set on the C or on another drive...

[SrGatoo]

@SoftFever Just wanted to thank you for your work.

Been trying OrcaSlicer and it's amazing, great job!

[rfield19]

Hi, I'm trying to compile this on a Mac m1 running Sonoma (ie newer version of xcode), and am getting the following error.
Is this anything that can be easily adjusted at my end (ie a version check in one of the files)?
I did a quick grep for Xcode but didn't find anything (although that doesn't mean much - I know just enough to be dangerous!)
`
[ 95%] Completed 'dep_wxWidgets'
[ 95%] Built target dep_wxWidgets
[100%] Built target dep_OCCT
[100%] Built target deps
building studio...
CMake Error:
Xcode 1.5 not supported.

CMake Error: Could not create named generator Xcode
`

[SoftFever]

Your CMake don't support Xcode 1.5.
Probably your CMake version is too old.
Try to update it to the latest.

[kieraneglin]

@rfield19 If you're sure XCode has been downloaded, run sudo xcodebuild -license then xcodebuild -runFirstLaunch. That got it working for me

[rfield19]

thanks @kieraneglin I'll give that a go.

[SoftFever]

Try this @patofoto

cd deps/build_arm64 
rm -rf dep_OCCT-prefix
make dep_OCCT

[patofoto]

@SoftFever Thank you. Will try and report back.

[patofoto]

No success yet. Getting this when trying above suggestion.
make dep_OCCT.txt

[fr3ak2402]

I have the same problem with my macOS systems...

No matter what platform you want to compile this for, it always fails on the dep_OCCT...

[rfield19]

@SoftFever No luck on compiling on Sonoma after ensuring cmake is up to date unfortunately.
Don't worry though, not important in the slightest - I can compile on an older machine.

Thanks for an excellent bit of software by the way - Orca is now my favourite slicer :)

[patofoto]

I second that emotion. Orca Slicer is my favorite slicer too!!!

[thewildmage]

I had some really random troubles compiling on arm64 MacOS. I'd get messages saying random libraries couldn't install, but it never seemed to be the same ones. At one point even, after having successfully built the dependencies dozens of times, they just randomly broke. What fixed it for me was:

1. rm -rf build_arm64 directory
2. rm -rf deps/build_arm64
3. Reboot my laptop
4. Try ./build_release_macos.sh -a arm64 again

Rebooting was important for me; I'd tried just removing the aforementioned directories, but that alone didn't work. I suspect that a partial dependency build left things hanging around in some way that caused trouble, and that these dangling pieces weren't freed up until the reboot.

[patofoto]

@thewildmage also tried your method. still no success. thanks

logs.txt

[MACCAMENZIES]

Im having issues trying to get Orca Slicer running on Fedora Linux. No problems when i do it in Ubuntu with the app image. Just not sure how to go about it with the rpm type system.

[patofoto]

Good morning @SoftFever. Downloaded fresh code today after I read you had pushed some fixes on Mac build. I am getting a dep_MPFR error now.

sh build_release_macos.txt

[odie5533]

Can you not use the pre-compiled deps from https://github.com/SoftFever/FileSharing/releases/download/OrcaSlicer_deps_Mar/OrcaSlicer_dep_mac_arm64_11-03-2023.tar.gz? I used the pre-compiled deps for compiling on Windows and it went much faster than building them myself.

Your error indicates you're missing aclocal. Have you installed automake with brew install automake?

There's M1 builds at https://github.com/SoftFever/OrcaSlicer/actions/workflows/build_mac_arm64.yml if you only want nightly style builds.

[SoftFever]

@patofoto
The log didn't say what's the exact error the MPFR has.
Can you try this?

cd deps/build_arm64  
rm -rf dep_MPFR-prefix
make dep_MPFR

If you error persists, you will need to check the build log inside dep_MPFR-prefix folder.

[odie5533]

Successfully built on Windows 11.

1. Install Strawberry Perl. Install CMake. Install VS Studio 2019 Community.
   
2. Create C:\a\OrcaSlicer
3. CD to it cd C:\a\OrcaSlicer and then git clone https://github.com/SoftFever/OrcaSlicer.git into another subdirectory called OrcaSlicer
4. Extract https://github.com/SoftFever/FileSharing/releases/download/OrcaSlicer_deps_Mar/OrcaSlicer_dep_05May2023.zip to C:\a\OrcaSlicer\OrcaSlicer\OrcaSlicer_dep so it contains C:\a\OrcaSlicer\OrcaSlicer\OrcaSlicer_dep\usr\local\...
5. Copy the OrcaSlicer_dep folder to C:\a\OrcaSlicer\OrcaSlicer\deps\build so it contains C:\a\OrcaSlicer\OrcaSlicer\deps\build\OrcaSlicer_dep\usr\local\.... This was needed for FreeType.
6. Go to Start and run x64 Native Tools Command Prompt for VS 2019.
7. Run subst D: C:\ You must not have a D: drive before running this command. So if you have one, you must remove it in Disk Management.
8. cd /d D:\a\OrcaSlicer\OrcaSlicer
9. Run build_release.bat studio
10. After it finishes, you should have the release build in C:\a\OrcaSlicer\OrcaSlicer\build\OrcaSlicer and be able to run it!
11. You can open C:\a\OrcaSlicer\OrcaSlicer\build\OrcaSlicer.sln with Visual Studio Community 2019. Once open, right-click OrcaSlicer_app_gui and click Set as Startup Project. Then go to Build > Rebuild Solution.
12. Click the Local Windows Debugger button and OrcaSlicer should start!

[alukc]

thank so much you save me

[Pennylofers]

Hello, when I open this in Visual Studio 2019 and click Local Windows Debugger it says unable to create directory and also says the directory does not exist. It is trying to open it in the D folder and I did the subst thing and it worked so im not sure why visual studio is saying this?

[zkydf1011]

I am using VS 2022, and during the process of debugging build_delease_vs022.bat, it prompts that openssl is missing. I downloaded and installed it from the openssl official website, and configured the system environment variables in Windows 11. However, it prompts that Utils.hpp cannot find openssl/md5. h. The specific reason is currently unknown. I am seeking an answer. The openssl version is 3.2.6

[stasyan68]

I have tried all the compilation options, all possible solutions to the problem! but it didn't work out to create a file under windows.

[odie5533]

Did you try the instructions I wrote above? #1425 (comment)

What error are you getting? What steps did you take? We need more info to help.

[patofoto]

@SoftFever Please let me know if all my questions help or just keep you from getting to important stuff. I am just curious and always eager to learn new stuff so I jump in and try to stay afloat with stuff I don't know. Keep not succeeding with trying to compile for MacOS. Have tried all your suggestions.
Yesterday I decided to clone your repo and open it with VSCode to see if I get any more clues. I got this in the error pane:

[{
	"resource": "/opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/FindPackageHandleStandardArgs.cmake",
	"owner": "cmake-configure-diags",
	"severity": 8,
	"message": "CMake Error at /opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):Could NOT find Threads (missing: Threads_FOUND)",
	"source": "CMake (message)",
	"startLineNumber": 230,
	"startColumn": 1,
	"endLineNumber": 230,
	"endColumn": 10000,
	"relatedInformation": [
		{
			"startLineNumber": 600,
			"startColumn": 1,
			"endLineNumber": 600,
			"endColumn": 1000,
			"message": "In call to '_FPHSA_FAILURE_MESSAGE' here",
			"resource": "/opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/FindPackageHandleStandardArgs.cmake"
		},
		{
			"startLineNumber": 226,
<img width="1460" alt="Screenshot 2023-07-11 at 6 57 54 AM" src="https://github.com/SoftFever/OrcaSlicer/assets/37857628/083b9e7d-ee0c-46a3-b29b-e5c8d7a07ea6">

			"startColumn": 1,
			"endLineNumber": 226,
			"endColumn": 1000,
			"message": "In call to 'FIND_PACKAGE_HANDLE_STANDARD_ARGS' here",
			"resource": "/opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/FindThreads.cmake"
		},
		{
			"startLineNumber": 76,
			"startColumn": 1,
			"endLineNumber": 76,
			"endColumn": 1000,
			"message": "In call to 'find_package' here",
			"resource": "/opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/CMakeFindDependencyMacro.cmake"
		},
		{
			"startLineNumber": 118,
			"startColumn": 1,
			"endLineNumber": 118,
			"endColumn": 1000,
			"message": "In call to 'find_dependency' here",
			"resource": "/opt/homebrew/lib/cmake/boost_thread-1.82.0/boost_thread-config.cmake"
		},
		{
			"startLineNumber": 141,
			"startColumn": 1,
			"endLineNumber": 141,
			"endColumn": 1000,
			"message": "In call to 'find_package' here",
			"resource": "/opt/homebrew/lib/cmake/Boost-1.82.0/BoostConfig.cmake"
		},
		{
			"startLineNumber": 262,
			"startColumn": 1,
			"endLineNumber": 262,
			"endColumn": 1000,
			"message": "In call to 'boost_find_component' here",
			"resource": "/opt/homebrew/lib/cmake/Boost-1.82.0/BoostConfig.cmake"
		},
		{
			"startLineNumber": 594,
			"startColumn": 1,
			"endLineNumber": 594,
			"endColumn": 1000,
			"message": "In call to 'find_package' here",
			"resource": "/opt/homebrew/Cellar/cmake/3.26.4/share/cmake/Modules/FindBoost.cmake"
		},
		{
			"startLineNumber": 355,
			"startColumn": 1,
			"endLineNumber": 355,
			"endColumn": 1000,
			"message": "In call to 'find_package' here",
			"resource": "/Users/pato/Documents/GitHub/OrcaSlicer/CMakeLists.txt"
		}
	]
}]

Please tell me to stop asking if all this is not helpful.

[odie5533]

If your end goal is to contribute code to the repo then it's probably helpful to onboard you. But if you only want to compile macOS builds for personal use, then it's probably not helpful because the macOS Github Action is working for that purpose.

The error says you are missing Threads. So presumably the solution would be to get Threads installed and working or try to find out why it can't find it.

[patofoto]

@odie5533 Thanks for your answer. Unfortunately I don't know enough to contribute to the repo. Wish I did because I think this is an amazing project and would give it my time without a doubt. Will stop asking questions here as I really don't want to take advantage of the generosity shown so far and allow the real developers to continue making progress.

[patofoto]

@SoftFever Screen grab

[SoftFever]

Hey guys,

I was able to reproduce the issue in my new PC, and I think I've figured out the cause of OCCT issue here.

The patch was not applied properly to OCCT hence it was installed to the wrong location.
The result is that we will see all deps are successfully built but when building Orca Slicer it complains not able to find OCCT.

It should be fixed after this commit: b76be35

You can rebuild OCCT only by:

1. delete "deps\build\dep_OCCT-prefix" folder
2. CD to "deps\build" folder, run cmake --build . --config Release --target dep_OCCT
3. delete OrcaSlicer's build folder and build again.

[patofoto]

I wanted to post to just say I have been compiling successfully on MacOS for the past few weeks. I am using VSCode to pull all changes to my local repo and running the build_release_macos.sh from within VSCode.

[iStarComLab]

Не фига он не собирает!!!
`CMake Error at src/libslic3r/CMakeLists.txt:452 (find_package):
By not providing "FindOpenCASCADE.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"OpenCASCADE", but CMake did not find one.

Could not find a package configuration file provided by "OpenCASCADE" with
any of the following names:

OpenCASCADEConfig.cmake
opencascade-config.cmake

Add the installation prefix of "OpenCASCADE" to CMAKE_PREFIX_PATH or set
"OpenCASCADE_DIR" to a directory containing one of the above files. If
"OpenCASCADE" provides a separate development package or SDK, be sure it
has been installed.

-- Configuring incomplete, errors occurred!
2023-08-13 15:05:32.511 xcodebuild[90142:289463] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project OrcaSlicer.xcodeproj build -target ALL_BUILD -parallelizeTargets -configuration Release -hideShellScriptEnvironment

User defaults from command line:
HideShellScriptEnvironment = YES
IDEPackageSupportUseBuiltinSCM = YES

2023-08-13 15:05:32.532 xcodebuild[90142:289463] Writing error result bundle to /var/folders/mr/81j4fr8d7bjg3zbxq4jfnmk40000gn/T/ResultBundle_2023-13-08_15-05-0032.xcresult
xcodebuild: error: 'OrcaSlicer.xcodeproj' does not exist.
rm: ./OrcaSlicer.app: No such file or directory
cp: ../src/Release/OrcaSlicer.app: No such file or directory
rm: ./OrcaSlicer.app/Contents/Resources: No such file or directory
usage: cp [-R [-H | -L | -P]] [-fi | -n] [-aclpsvXx] source_file target_file
cp [-R [-H | -L | -P]] [-fi | -n] [-aclpsvXx] source_file ... target_directory
find: ./OrcaSlicer.app/: No such file or directory

[Done] exited with code=1 in 10328.737 seconds`

[patofoto]

Getting CMake errors. But compiles ok. Anything I should do or ignore?

[proc] Executing command: /opt/homebrew/bin/cmake --version
[proc] Executing command: /opt/homebrew/bin/cmake -E capabilities
[variant] Loaded new set of variants
[kit] Successfully loaded 5 kits from /Users/pato/.local/share/CMakeTools/cmake-tools-kits.json
[proc] Executing command: /usr/bin/clang -v
[proc] The command: ninja --version failed with error: Error: spawn ninja ENOENT
[proc] The command: ninja-build --version failed with error: Error: spawn ninja-build ENOENT
[proc] Executing command: /opt/homebrew/bin/cmake -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles"
[proc] The command: /opt/homebrew/bin/cmake -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles" exited with code: 1
[main] Configuring project: OrcaSlicer 
[proc] Executing command: /opt/homebrew/bin/cmake --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] -- CMAKE_OSX_DEPLOYMENT_TARGET: 11.3
[cmake] -- Orca: IS_CROSS_COMPILE: FALSE
[cmake] -- SLIC3R_ASAN: OFF
[cmake] -- SLIC3R_BUILD_SANDBOXES: OFF
[cmake] -- SLIC3R_BUILD_TESTS: OFF
[cmake] -- SLIC3R_DESKTOP_INTEGRATION: ON
[cmake] -- SLIC3R_FHS: OFF
[cmake] -- SLIC3R_GTK: 2
[cmake] -- SLIC3R_GUI: ON
[cmake] -- SLIC3R_MSVC_COMPILE_PARALLEL: ON
[cmake] -- SLIC3R_MSVC_PDB: ON
[cmake] -- SLIC3R_PCH: ON
[cmake] -- SLIC3R_PERL_XS: OFF
[cmake] -- SLIC3R_PROFILE: OFF
[cmake] -- SLIC3R_STATIC: ON
[cmake] -- SLIC3R_WX_STABLE: OFF
[cmake] -- SLIC3R_STATIC: ON
[cmake] -- CMAKE_PREFIX_PATH: (default)
[cmake] -- PROJECT_SOURCE_DIR: /Users/pato/Documents/GitHub/OrcaSlicer
[cmake] -- CMAKE_MODULE_PATH: /Users/pato/Documents/GitHub/OrcaSlicer/cmake/modules/
[cmake] -- LIBDIR: /Users/pato/Documents/GitHub/OrcaSlicer/src
[cmake] -- LIBDIR_BIN: /Users/pato/Documents/GitHub/OrcaSlicer/build/src
[cmake] OS X SDK Path: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk
[cmake] OS X Deployment Target: 11.3
[cmake] CMake Error at /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
[cmake]   Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem thread
[cmake]   log locale regex chrono atomic date_time iostreams program_options)
[cmake]   (Required is at least version "1.66")
[cmake] Call Stack (most recent call first):
[cmake]   /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
[cmake]   /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindBoost.cmake:2393 (find_package_handle_standard_args)
[cmake]   CMakeLists.txt:394 (find_package)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: /opt/homebrew/bin/cmake --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles" exited with code: 1

[patofoto]

Still getting errors when opening the repo:

[cmake] CMake Error at /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
[cmake]   Could NOT find Boost (missing: Boost_INCLUDE_DIR system filesystem thread
[cmake]   log locale regex chrono atomic date_time iostreams program_options)
[cmake]   (Required is at least version "1.66")
[cmake] Call Stack (most recent call first):
[cmake]   /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
[cmake]   /opt/homebrew/Cellar/cmake/3.29.6/share/cmake/Modules/FindBoost.cmake:2393 (find_package_handle_standard_args)
[cmake]   CMakeLists.txt:394 (find_package)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: /opt/homebrew/bin/cmake --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles" exited with code: 1

Think they are about Boost?. Repo compiles ok but not sure if I should just ignore this.

[patofoto]

@igiannakas Apologies for the include here. I was wondering if you happen be having issues compiling for Mac?. I have been getting CMake errors (look at posts above) but have have been able to compile anyway. Today I can't compile anymore. This is what I get:

[driver] Switching to kit: Clang 15.0.0 arm64-apple-darwin23.5.0
[proc] Executing command: /usr/bin/clang -v
[proc] The command: ninja --version failed with error: Error: spawn ninja ENOENT
[proc] The command: ninja-build --version failed with error: Error: spawn ninja-build ENOENT
[driver] Removing /Users/pato/Documents/GitHub/OrcaSlicer/build/CMakeCache.txt
[driver] Removing /Users/pato/Documents/GitHub/OrcaSlicer/build/CMakeFiles
[main] Configuring project: OrcaSlicer 
[proc] Executing command: /opt/homebrew/bin/cmake -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ --no-warn-unused-cli -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles"
[cmake] Not searching for unused variables given on the command line.
[cmake] -- CMAKE_OSX_DEPLOYMENT_TARGET: 11.3
[cmake] -- The C compiler identification is AppleClang 15.0.0.15000309
[cmake] -- The CXX compiler identification is AppleClang 15.0.0.15000309
[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: /usr/bin/clang - skipped
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: /usr/bin/clang++ - skipped
[cmake] -- Detecting CXX compile features
[cmake] -- Detecting CXX compile features - done
[cmake] -- Orca: IS_CROSS_COMPILE: FALSE
[cmake] -- SLIC3R_ASAN: OFF
[cmake] -- SLIC3R_BUILD_SANDBOXES: OFF
[cmake] -- SLIC3R_BUILD_TESTS: OFF
[cmake] -- SLIC3R_DESKTOP_INTEGRATION: ON
[cmake] -- SLIC3R_FHS: OFF
[cmake] -- SLIC3R_GTK: 2
[cmake] -- SLIC3R_GUI: ON
[cmake] -- SLIC3R_MSVC_COMPILE_PARALLEL: ON
[cmake] -- SLIC3R_MSVC_PDB: ON
[cmake] -- SLIC3R_PCH: ON
[cmake] -- SLIC3R_PERL_XS: OFF
[cmake] -- SLIC3R_PROFILE: OFF
[cmake] -- SLIC3R_STATIC: ON
[cmake] -- SLIC3R_WX_STABLE: OFF
[cmake] -- SLIC3R_STATIC: ON
[cmake] -- CMAKE_PREFIX_PATH: (default)
[cmake] -- PROJECT_SOURCE_DIR: /Users/pato/Documents/GitHub/OrcaSlicer
[cmake] -- CMAKE_MODULE_PATH: /Users/pato/Documents/GitHub/OrcaSlicer/cmake/modules/
[cmake] -- LIBDIR: /Users/pato/Documents/GitHub/OrcaSlicer/src
[cmake] -- LIBDIR_BIN: /Users/pato/Documents/GitHub/OrcaSlicer/build/src
[cmake] OS X SDK Path: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk
[cmake] OS X Deployment Target: 11.3
[cmake] CMake Warning (dev) at CMakeLists.txt:394 (find_package):
[cmake]   Policy CMP0167 is not set: The FindBoost module is removed.  Run "cmake
[cmake]   --help-policy CMP0167" for policy details.  Use the cmake_policy command to
[cmake]   set the policy and suppress this warning.
[cmake] 
[cmake] This warning is for project developers.  Use -Wno-dev to suppress it.
[cmake] 
[cmake] -- Found Boost: /opt/homebrew/lib/cmake/Boost-1.85.0/BoostConfig.cmake (found suitable version "1.85.0", minimum required is "1.66") found components: system filesystem thread log locale regex chrono atomic date_time iostreams program_options
[cmake] -- Could NOT find TBB (missing: TBB_DIR)
[cmake] -- Falling back to MODULE search for TBB...
[cmake] CMake Error at /opt/homebrew/Cellar/cmake/3.30.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
[cmake]   TBB library cannot be found.  Consider set TBBROOT environment variable.
[cmake]   (missing: TBB_INCLUDE_DIRS TBB_LIBRARIES)
[cmake] Call Stack (most recent call first):
[cmake]   /opt/homebrew/Cellar/cmake/3.30.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)
[cmake]   cmake/modules/FindTBB.cmake.in:286 (find_package_handle_standard_args)
[cmake]   cmake/modules/FindTBB.cmake:19 (include)
[cmake]   CMakeLists.txt:429 (find_package)
[cmake] 
[cmake] 
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: /opt/homebrew/bin/cmake -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ --no-warn-unused-cli -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles" exited with code: 1

Are you having any issues?. Any light you can shed to my issue?. Apologies for not knowing what I am doing.

[patofoto]

Just to update this thread a bit. No success yet. Unable to compile on MacOS. Tried a fresh install of MacOS, VSCode and all dependencies. If anyone is experiencing issues with MacOS compile please share.

@SoftFever Any suggestions?

[igiannakas]

Why are you installing vs code on Mac? The project is Xcode based. Install the ide, u less you’ve already done so?

[patofoto]

Why are you installing vs code on Mac? The project is Xcode based. Install the ide, u less you’ve already done so?

I have been using VSCode IDE to compile using the build_release_macos.sh shell script for a while. Have only used Xcode once months ago out of curiosity. When I try to compile with Xcode now I get this:

Using a fresh repo

[igiannakas]

Delete your git repo download and re-clone. Then run the build sh script. It will generate the Xcode project file. Then you can open it and compile in Xcode. Also check to set the build target and debug levels in the target. https://www.youtube.com/watch?v=d7b9f3EEUeQ

[patofoto]

Followed your instructions. I still get errors and it will stop compiling. The build_arm64 folder does not get created so I don't have an .xcodeproj file to test. This is the output from the console after running build_release_macos.sh after a fresh new re-clone:

compile_output.txt

I know this is getting way too complicated now. Don't mean to burden you.

[patofoto]

Just updated to macOS Sequoia 15. Can't compile anymore. Getting this error:

CMake Error at /opt/homebrew/Cellar/cmake/3.30.3/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:233 (message):Could NOT find GLEW (missing: GLEW_INCLUDE_DIRS GLEW_LIBRARIES)

Will try downloading GLEW manually with Homebrew

[patofoto]

Installed GLEW and now get this:

cmake] -- FindGLEW: GLEW_USE_STATIC_LIBS: ON.
[cmake] -- FindGLEW: GLEW_INCLUDE_DIR: /opt/homebrew/include
[cmake] -- FindGLEW: GLEW_INCLUDE_DIRS: /opt/homebrew/include
[cmake] -- FindGLEW: CMAKE_FIND_LIBRARY_SUFFIXES for SHARED: .dylib;.so
[cmake] -- FindGLEW: CMAKE_FIND_LIBRARY_SUFFIXES for STATIC: .a
[cmake] -- FindGLEW: GLEW_SHARED_LIBRARY_RELEASE: /opt/homebrew/lib/libGLEW.dylib
[cmake] -- FindGLEW: GLEW_STATIC_LIBRARY_RELEASE: /opt/homebrew/lib/libGLEW.a
[cmake] -- FindGLEW: GLEW_SHARED_LIBRARY_DEBUG: GLEW_SHARED_LIBRARY_DEBUG-NOTFOUND
[cmake] -- FindGLEW: GLEW_STATIC_LIBRARY_DEBUG: GLEW_STATIC_LIBRARY_DEBUG-NOTFOUND
[cmake] -- FindGLEW: GLEW_SHARED_LIBRARY: /opt/homebrew/lib/libGLEW.dylib
[cmake] -- FindGLEW: GLEW_STATIC_LIBRARY: /opt/homebrew/lib/libGLEW.a
[cmake] -- FindGLEW: GLEW_LIBRARIES: /opt/homebrew/lib/libGLEW.a
[cmake] -- FindGLEW: GLEW_VERSION_MAJOR: 2
[cmake] -- FindGLEW: GLEW_VERSION_MINOR: 2
[cmake] -- FindGLEW: GLEW_VERSION_MICRO: 0
[cmake] -- FindGLEW: GLEW_VERSION: 2.2.0
[cmake] -- Found GLEW: /opt/homebrew/include (found version "2.2.0")
[cmake] -- FindGLEW: Creating GLEW::glew_s imported target.
[cmake] -- FindGLEW: Creating GLEW::GLEW imported target.
[cmake] GLEW_ROOT: 
[cmake] -- Configuring incomplete, errors occurred!
[cmake] CMake Error at CMakeLists.txt:541 (find_package):
[cmake]   By not providing "Findglfw3.cmake" in CMAKE_MODULE_PATH this project has
[cmake]   asked CMake to find a package configuration file provided by "glfw3", but
[cmake]   CMake did not find one.
[cmake] 
[cmake]   Could not find a package configuration file provided by "glfw3" with any of
[cmake]   the following names:
[cmake] 
[cmake]     glfw3Config.cmake
[cmake]     glfw3-config.cmake
[cmake] 
[cmake]   Add the installation prefix of "glfw3" to CMAKE_PREFIX_PATH or set
[cmake]   "glfw3_DIR" to a directory containing one of the above files.  If "glfw3"
[cmake]   provides a separate development package or SDK, be sure it has been
[cmake]   installed.
[cmake] 
[cmake] 
[proc] The command: /opt/homebrew/bin/cmake -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -DCMAKE_C_COMPILER:FILEPATH=/usr/bin/clang -DCMAKE_CXX_COMPILER:FILEPATH=/usr/bin/clang++ --no-warn-unused-cli -S/Users/pato/Documents/GitHub/OrcaSlicer -B/Users/pato/Documents/GitHub/OrcaSlicer/build -G "Unix Makefiles" exited with code: 1

Don't know if I should continue digging deeper or if I will break something.

[patofoto]

@SoftFever I know you must be super busy. Any quick tips to point me in the right direction?

[igiannakas]

@SoftFever I know you must be super busy. Any quick tips to point me in the right direction?

I’ve successfully compiled orca on macOS 15 without a hitch. The default script worked well. Suggest doing a clean wipe ( a UTM vm can help here to get you an “new” system without having to break your own) and starting again with the dependencies, then cloning the GitHub repository and running the Mac OS build script. It should work straight away.

[Mqrius]

Just wanted to mention here that I couldn't get things to work on Windows with Visual Studio 2019. I got the wxwidget issue I see mentioned above, as well as a few other things when trying things. Also, Visual Studio 2019 Community is kind of a hassle to obtain, since Microsoft doesn't actually offer it freely anymore, and really tries to get you to use 2022.

Here's what did work for me:

• Install Visual Studio Community 2022 (it's the free version) from https://visualstudio.microsoft.com/downloads/ , the version I got is 17.11.4
• • In the Visual Studio Community installer, in the Workload selection, select "Desktop development with C++" and leave all the optional defaults selected. That's probably more than needed, but it works. For me it selected
• • • MSVC v143
• • • C++ ATL for latest v143
• • • Security Issue Analysis
• • • C++ Build Insights
• • • Just-In-Time debugger
• • • C++ profiling tools
• • • C++ CMake tools for Windows
• • • Test Adapter for Boost.Test
• • • Test Adapter for Google Test
• • • Live Share
• • • IntelliCode
• • • C++ AddressSanitizer
• • • Windows 11 SDK (10.0.22621.0) (Though I think for the build it may have been using a Windows 10 SDK that was still installed from VS2019?)
• • • vcpkg package manager
• • • GitHub Copilot
• I did not install my own CMake, it is installed automatically with the Visual Studio C++ Workload. Both the 2019 and the 2022 CMake are 3.14 or later, so this should be acceptable. (IIRC I had some issues when I tried to use my own CMake when I tried it for the 2019 install, so this doesn't seem worth it.)
• I already had installed Git, nothing special, my version is 2.32.0.
• Install Strawberry Perl
• From the Windows start menu, run "x64 Native Tools Command Prompt for VS 2022"
• Navigate to where you want to download OrcaSlicer, eg cd C:\
• git clone https://github.com/SoftFever/OrcaSlicer.git
• cd OrcaSlicer
• git lfs pull
• build_release2022.bat > buildlog.txt 2>&1
• • You won't see any output cos it's all sent to "buildlog.txt", that's intentional so you can later share that file if it doesn't work. The compiling takes at least half an hour.

I bolded crucial differences from the official readme instructions. Maybe it's time to retire VS2019?

[re3Dev]

I followed your instructions and am still getting errors. Here is the build log:
buildlog.txt

[dannutu]

Did anybody manage to connect from Orca running on an ARM CPU (raspberry) to a Bambu printer over the (LAN-only) network?
I'm asking because the slicer nags me to download and install the Bambu network plugin, I allow it to do that, it tells me that it was "successful", but then when I look in ~/.config/OrcaSlicer/plugins/ the three shared library (.so) files there are for x86-64!

[HipsterJack]

Trying to build for Linux Mint 21.3 and running into an error with OpenCV - getting the output below. Tried with stable and nightly, same problem. I'm not quite following the error it seems to be missing some files/directories that are expected. Apologies if this is an easy one, first time building from source as the appimage wasn't playing nice at all for me either.

-- Downloading...
   dst='/home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/../DL_CACHE/OpenCV/4.6.0.tar.gz'
   timeout='none'
   inactivity timeout='none'
-- Using src='https://github.com/opencv/opencv/archive/refs/tags/4.6.0.tar.gz'
-- verifying file...
       file='/home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/../DL_CACHE/OpenCV/4.6.0.tar.gz'
-- Downloading... done
-- extracting...
     src='/home/username/Downloads/OrcaSlicer-nightly-builds/deps/DL_CACHE/OpenCV/4.6.0.tar.gz'
     dst='/home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/dep_OpenCV-prefix/src/dep_OpenCV'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[78/185] Performing patch step for 'dep_OpenCV'
FAILED: dep_OpenCV-prefix/src/dep_OpenCV-stamp/dep_OpenCV-patch /home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/dep_OpenCV-prefix/src/dep_OpenCV-stamp/dep_OpenCV-patch 
cd /home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/dep_OpenCV-prefix/src/dep_OpenCV && git apply --directory deps/build/dep_OpenCV-prefix/src/dep_OpenCV --verbose --ignore-space-change --whitespace=fix /home/username/Downloads/OrcaSlicer-nightly-builds/deps/OpenCV/0001-vs2022.patch && /usr/bin/cmake -E touch /home/username/Downloads/OrcaSlicer-nightly-builds/deps/build/dep_OpenCV-prefix/src/dep_OpenCV-stamp/dep_OpenCV-patch
Checking patch deps/build/dep_OpenCV-prefix/src/dep_OpenCV/cmake/templates/OpenCVConfig.root-WIN32.cmake.in...
error: deps/build/dep_OpenCV-prefix/src/dep_OpenCV/cmake/templates/OpenCVConfig.root-WIN32.cmake.in: No such file or directory
Checking patch deps/build/dep_OpenCV-prefix/src/dep_OpenCV/cmake/OpenCVDetectCXXCompiler.cmake...
error: deps/build/dep_OpenCV-prefix/src/dep_OpenCV/cmake/OpenCVDetectCXXCompiler.cmake: No such file or directory
[79/185] Performing build step for 'dep_TBB'```

[scotthep]

I am getting a similar error on the AUR orca-slicer build:
https://aur.archlinux.org/packages/orca-slicer
orca_slicer.txt
This pulls the 2.2.0 release code base.

[yw4z]

I switched to new PC after a long time. I'm tring to build orca but get this error

-- Boost toolset is unknown (compiler MSVC 19.42.34435.0)
CMake Error at deps/Build/OrcaSlicer_dep/usr/local/lib/cmake/Boost-1.78.0/BoostConfig.cmake:141 (find_package):
  Could not find a package configuration file provided by
  "boost_program_options" (requested version 1.78.0) with any of the
  following names:

    boost_program_optionsConfig.cmake
    boost_program_options-config.cmake

Windows 11 / Visual Studio 2022
Installed cMake, Strawberry and copied OrcaSlicer_dep folder
there is a additional boost package on https://github.com/SoftFever/OrcaSlicer_deps/releases but it looks like already bundled in repo. do i have to copy it?
am i missing something?

[scotthep]

The project releases Nightly builds for Windows:
https://github.com/SoftFever/OrcaSlicer/releases

Unless you're modifying code or just want the experience, the nightly build will not differ from your build.

[CristianGTR97]

@Mqrius I followed your method, and I think it worked, but I'm don't know where can I see the installer or executable file for orcaslicer after it is compiled. Where are those files supposed to be located?

[CristianGTR97]

I tried again and I'm getting this error at the end:

-- Configuring incomplete, errors occurred!

C:\OrcaSlicer\OrcaSlicer\build>cmake --build . --config Release --target ALL_BUILD -- -m
MSBuild version 17.12.12+1cce77968 for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: ALL_BUILD.vcxproj
C:\OrcaSlicer\OrcaSlicer
MSBuild version 17.12.12+1cce77968 for .NET Framework
MSBUILD : error MSB1009: Project file does not exist.
Switch: install.vcxproj

How can I solve this?

buildlog.txt

[ghost]

log.txt
Please help me check this error, there is a boost can not find the thread, need I specify the boost library path

[dudu631]

I did try to compile this for hours, compiled manually the wxWidgets, fixed a lot of errors along the way and still can't compile this. I did delete build and deps/build many times also. I had most of the problems windows users reported here on this thread (wxWidgets, Boost, Curl, JCS_EXT_RBGBA).

Windows 11, VS2022, Strawberry Perl.

Tried cloning again many times, fresh compilation. Nothing worked.

What am I missing? Is this supposed to be this hard?

[christopher-lambe]

#1425 (comment)

[ianalexis]

CMake 4.0 Removes compatibility with CMake < 3.5 so its not compiling. Stay in 3.31.6

[christopher-lambe]

Strawberry Perl and VS will install their own versions of cmake and append the path system environment variable. Depending on which version has higher priority the build will fail. Check with cmake --version, then if needed check with where cmake and change the path system environment variable.

This will prevent the error:
CMake Error at C:/Strawberry/c/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find wxWidgets (missing: wxWidgets_LIBRARIES

EDIT: forgot to mention the exact cmake version needed 3.31.x. PR from not me mentions this #9383

[macifysoft]

You can choose not install cmake from visual studio when installing the c++ tool under components just deselect it and install the cmake from cmake.org. It will help when setting up cmake as if you install cmake from the website then install VS version it will take over and you end up running v4

[lordbah]

Does anyone have a writeup of doing a debug build of OrcaSlicer on Ubuntu 22.04? I am SO many browser tabs deep on this and making no progress. In fact I'm making regress.
I built it debug (-b) the first time (I thought!), but under vscode it wasn't resolving breakpoints, and when I ran readelf on any .o file there was no debug info in it. Since then I've been trying various things, including trying to let vscode figure out how to do the build on its own based on the CMakeFile and some extension, but I haven't been able to get a single successful build - even when I remove build/ and deps/build/ and run build_linux.sh the same way I did the first time. (The -c clean build doesn't seem to actually remove anything)

[ianalexis]

I understand that you can't compile from VSCODE, much less vscode in Ubuntu.
For Ubuntu, there's a section in the how-to-build guide.
I personally don't have experience compiling Orca from Linux, but I do from Windows, and it's a VS2022 project (not CSVODE).

[lordbah]

It's true that I can't build it from vscode. It's also true that when I build it with build_linux.sh, following that guide but adding -b, there were no debug symbols, which was really the only reason I even tried to build in vscode. I also read somewhere that debug build isn't well supported, I was just hoping to find some user who had done it.
Edit of an AMS slot self-erases in about 5 seconds, and I was annoyed enough that I thought I'd try to figure out why. I need breakpoints to help me figure out what gets called when.

[Poopi]

I was struggling with compilation on macOS of OrcaSlicer few months ago. During the linking phase I kept getting error "ld: library 'GL' not found". It was't urgent so I left it and played on Linux. Today with a fresh mind I quickly spotted the problem. It happens when you have XQuartz server being installed on the system. I had the official one ( not sure if the one from brew causing the issue but I would be so ) - I simply unlinked /opt/X11 folder and everything went as smooth as butter. Would be good to add a note to the wiki/how to as I'm not only the one with such an issue.