Arch Linux User Repository

@michael.gruz please adopt the curaengine package as this will be merged into curaengine

You may not need the older compiler since conan v1.60.0 (11-May-2023).

From their changelog:

Fix: Add gcc 13 to default settings.yml. #13848

I will try to build libarcus from source again later today…

@TimTechDev It is progress, now I was successful compiling curaengine binary. It's time to change the scripts and release a version for wider testing.

So I'm wondering whether to put the build version from the sources or the ready binary? Compilation, especially the first time using "conan", is very complicated - at least it was for me. We can take a chance with the sources, and if it doesn't work for you, I'll release the already compiled binary instead of the sources.

@batot To fix ERROR: Invalid setting '13' is not a valid 'settings.compiler.version' use gcc12

export CC=gcc-12 CXX=g++-12
export CONAN_NON_INTERACTIVE=true

conan config install https://github.com/ultimaker/conan-config.git
conan profile new default --detect --force
conan install . --build=missing --update
cd curaengine-${pkgver}
cmake --preset release
cmake --build --preset release

I am currently tying to fix https://aur.archlinux.org/packages/arcus :)

I undertook to create this package because I thought it would be easy. It turned out that building this package is the hardest thing I've ever done with AUR. Despite the obstacles, I devoted a lot of private time to explore the knowledge to create this package. I immediately advise against trying to compile it from github sources - it's too complicated, as @BillFleming mentioned.

I'm currently stuck here:

$ conan install . --build=missing --update ERROR: Invalid setting '13' is not a valid 'settings.compiler.version' value. Possible values are ['4.1', '4.4', '4.5', '4.6', '4.7', '4.8', '4.9', '5', '5.1', '5.2', '5.3', '5.4 ', '5.5', '6', '6.1', '6.2', '6.3', '6.4', '6.5', '7', '7.1', '7.2', '7.3', '7.4', '7.5', '8', '8.1', '8.2', '8.3', '8.4', '9', '9.1', '9.2', '9.3', '9.4', '10', '10.1 ', '10.2', '10.3', '11', '11.1', '11.2', '11.3', '12', '12.1', '12.2'] Read "http://docs.conan.io/en/latest/faq/troubleshooting.html#error-invalid-setting"

I've already reported a compilation problem. Why am I writing this to you? I wanted you to know that I am fighting, so far I have not given up.

If someone managed to go further than me or compile this package - a challenge for hardcore people. ;) Please write to me, I will add you permissions, maybe together we will be able to build this package.

@BillFleming do you have this same problem like me or something other?

I have been so far unable to build this with their current conan instructions on arch. From what I can gather currently:

• You need to install conan1 aur package (v1.59), it will replace conan v2 on your system so hope you don't need conan V2 to build anything else. Directions are outdated and don't mention that conan v2 won't work.
• Every single command they have in documentation/issue tracker fails to work on conan v2. Command format had many changes.
• You need to install conan profiles manually into your home directory
• They provide a github download link for the profiles, but the file names don't match the directions so it will fail.
• The provided profiles at the link are actually conan v2 profiles, so c++ version setting and other settings will be missing and it won't work.
• Haven't found link to the correct older conan v1.56 profiles or taken the time to figure them out from old github check-ins. They don't have proper releases/tags on that repo.

It probably would be easier to build the latest V4.XX versions with cmake and supplying the missing variables into it.

Oof well that does sound annoying. Well, feel free to pick this back up again if you can get it to build somehow.

Yeeeah so I though I would take a look into this, but this is a huge mess right now... Ultimaker seems to be in the middle of refactoring their build system to use Conan instead of just CMake.

https://github.com/Ultimaker/CuraEngine/wiki/Building-CuraEngine-From-Source

And then their conan config repo mentions that they're planning to migrate to Conan V2 soon, so probably not really worth looking much into this until then...

Anyway, some of the things that might have to be done are:

• making a separate umbase package for their common Conan config (which also seems to include their standardprojectsettings included in the CMakeLists
• possibly making a separate sipbuildtool package as the conanfile seems to require that (haven't really looked into exactly how necessary it is), or just add this into this package
• getting conan to actually use these instead of trying to fetch them from a remote

Is this still maintained?