I don't know what it is with this one, but it's finding the wrong one. We specify through the prefix that it should search in the cura-build-environment first, but apparently it's not listening to that. As a result it's getting Python 3.6, and then stops because it can't find the headers for that version. It wouldn't need the headers in this case, but if it didn't crash here it would crash during the run time because libArcus and libSavitar have been linked to Python 3.5.
According to what I found in the docs[1], there is no "DIRECTORY" available as <type>.
Therefore, correcting it to "PATH", which is according to the docs correct.
At the moment I'm getting the following error[2]:
-----------
CMake Warning (dev) at CMakeLists.txt:8 (set):
implicitly converting 'DIRECTORY' to 'STRING' type.
This warning is for project developers. Use -Wno-dev to suppress it.
CMake Warning (dev) at CMakeLists.txt:9 (set):
implicitly converting 'DIRECTORY' to 'STRING' type.
This warning is for project developers. Use -Wno-dev to suppress it.
---------------
[1] https://cmake.org/cmake/help/v3.6/command/set.html
[2] https://launchpadlibrarian.net/464670600/buildlog_ubuntu-focal-amd64.cura_1%3A4.5~202002121434~rev4433~pkg330~ubuntu20.04.1_BUILDING.txt.gz
Adds support to install Cura to an alternative path, while generating a correct .desktop file for it.
* Renaming cura.desktop to cura.desktop.in
* CMAKE: Generate .desktop from .desktop.in
* Replace hardcoded paths with FULL_PATHs
* Tell CMake to generate cura.desktop
* CMake: Set full paths for .desktop generation
* It tells CMake where to find the .desktop.in is and where to store the result.
For example, if the community distributes Cura in a different way, they
can set CURA_BUILDTYPE via 'cmake -DCURA_BUILDTYPE=' and whenever Cura
is launched " (PPA)" will be appended. Of course, this could be done by
appending " (PPA)" to CURA_VERSION, but in case of my Ubuntu/Debian
packaging it will only need one modification in debian/changelog to
change the version. During build (debian/rules) this version will be
read from debian/changelog.
Changing the version number across different files, is a waste of time.
Finally, we can use that field in the future to indicate debug or other
other special builds.
