-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:5 (find_package):
By not providing "Findnest2d.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "nest2d", but
CMake did not find one.
Could not find a package configuration file provided by "nest2d" with any
of the following names:
nest2dConfig.cmake
nest2d-config.cmake
Add the installation prefix of "nest2d" to CMAKE_PREFIX_PATH or set
"nest2d_DIR" to a directory containing one of the above files. If "nest2d"
provides a separate development package or SDK, be sure it has been
installed.
-- Configuring incomplete, errors occurred!
See also "/home/user/.cache/yay/python-pynest2d-git/src/pynest2d/build/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
Aborting...
-> error making: python-pynest2d-git
Search Criteria
Package Details: cura-git 4.8.beta.r99.g5ab4062ce-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cura-git.git (read-only, click to copy) |
---|---|
Package Base: | cura-git |
Description: | A full software solution for 3D printing aimed at RepRaps and the Ultimaker. |
Upstream URL: | https://github.com/Ultimaker/Cura |
Keywords: | 3dprint cura ultimaker |
Licenses: | GPL3 |
Conflicts: | cura |
Provides: | cura |
Submitter: | ad1217 |
Maintainer: | None |
Last Packager: | ad1217 |
Votes: | 15 |
Popularity: | 0.000229 |
First Submitted: | 2014-11-24 06:53 (UTC) |
Last Updated: | 2020-11-09 02:19 (UTC) |
Dependencies (24)
- curaengine-gitAUR
- libarcus-gitAUR
- libsavitarAUR (libsavitar-gitAUR)
- python (python37AUR, python311AUR, python310AUR)
- python-certifi
- python-numpy (python-numpy-flameAUR, python-numpy-gitAUR, python-numpy1AUR, python-numpy-mkl-tbbAUR, python-numpy-mklAUR, python-numpy-mkl-binAUR)
- python-protobuf (python-protobuf-gitAUR)
- python-pynest2d-gitAUR
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR)
- python-requests
- python-sentry_sdk
- qt5-graphicaleffects (qt5-graphicaleffects-gitAUR)
- qt5-quickcontrols (qt5-quickcontrols-gitAUR)
- qt5-quickcontrols2 (qt5-quickcontrols2-gitAUR)
- qt5-svg (qt5-svg-gitAUR)
- uranium-gitAUR
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- cura-binary-data-gitAUR (optional) – Firmwares and translations
- cura-fdm-materials-gitAUR (optional) – Default Materials
- Show 4 more dependencies...
Required by (6)
- cura-plugin-octoprint-git (requires cura)
- cura-plugin-orientation-git (requires cura)
- cura-resources-fabtotum-git (requires cura)
- discovery200-files (requires cura) (optional)
- inkscape-paths2openscad (requires cura) (optional)
- libarcus-git (requires cura) (make)
Sources (1)
luntik2012 commented on 2022-09-29 10:10 (UTC) (edited on 2022-09-29 10:10 (UTC) by luntik2012)
tornado99 commented on 2022-05-27 11:14 (UTC) (edited on 2022-05-27 11:17 (UTC) by tornado99)
build error No such file or directory make[2]: [CMakeFiles/sip_pyArcus.dir/build.make:101: pyArcus.so] Error 1 make[2]: Deleting file 'pyArcus.so' make[1]: [CMakeFiles/Makefile2:140: CMakeFiles/sip_pyArcus.dir/all] Error 2 make: [Makefile:136: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...
vanja_z commented on 2022-01-03 16:16 (UTC)
I could not build the package today because I was getting the error,
include could not find load file:
UraniumTranslationTools
I tried rebuilding all of the VCS package dependencies including uranium-git but it did not help. The problem is that uranium-git places UraniumTranslationTools.cmake into /usr/share/cmake-3.22/Modules which is an otherwise empty directory. All of the other cmake modules in my system are located in /usr/share/cmake/Modules so as a workaround I created a symlink.
sudo ln -s /usr/share/cmake-3.22/Modules/UraniumTranslationTools.cmake /usr/share/cmake/Modules/UraniumTranslationTools.cmake
My question is, what is the correct location for cmake modules? On my system there is nothing other than the aforementioned file under /usr/share/cmake-3.22 and everything else is simply under /usr/share/cmake. Is this a bug that should be reported upstream to uranium devs? Or is it a packaging issue specific to Arch that we should take care of with the AUR package uranium-git?
Thanks, Vanja
Meganium97 commented on 2021-10-04 19:55 (UTC)
I'm not able to install, getting the error: File "/usr/bin/cura", line 21, in <module> from UM.Platform import Platform ModuleNotFoundError: No module named 'UM'
What do I need to do?
VanClaussen commented on 2021-07-23 12:56 (UTC)
cura-fdm-materials-git isn't an optional dependence because you can't use cura without it (can't create materials or options for materials).
a36233 commented on 2021-04-21 11:06 (UTC)
python-keyring dependency missing
stratus_ss commented on 2020-12-11 23:57 (UTC)
After a recent update this week cura no longer opens:
Traceback (most recent call last):
File "/usr/bin/cura", line 23, in <module>
import Arcus # @UnusedImport
ModuleNotFoundError: No module named 'Arcus'
I'm not actually sure how to fix this one
ad1217 commented on 2020-11-09 02:21 (UTC)
@uncholowapo: Should be fixed now, thanks for the heads up!
uncholowapo commented on 2020-11-08 14:01 (UTC) (edited on 2020-11-08 14:03 (UTC) by uncholowapo)
Got this error when starting Cura that was compiled today. Looks like neither the libnest2d lib nor the python binding are in the official repos nor in AUR
Traceback (most recent call last):
File "/usr/bin/cura", line 25, in <module>
import pynest2d # @UnusedImport
ModuleNotFoundError: No module named 'pynest2d'
Pinned Comments
ad1217 commented on 2018-02-14 18:10 (UTC) (edited on 2020-03-01 18:53 (UTC) by ad1217)
This is a VCS package, which means that when you build it, it will set the pkgver based on the latest version in the upstream repo. The only thing bumping version numbers here does is make people who already have it installed see that it needs updating (assuming they use an AUR helper). Bumping it here frequently is both pointless, as anyone can just rebuild the package(s) to get the latest, and annoying, since the git repo updates many times a day. If you want to get the latest, I'd suggest running something like
to rebuild this and all related packages.Generally, I will only update these packages when something changes in the build process such that they don't work, dependencies change, or a major version is released.