Re: git: 75ac7903573c - main - graphics/darktable: Use GCC as the compiler instead of LLVM
- Reply: Jean-Sébastien_Pédron : "Re: git: 75ac7903573c - main - graphics/darktable: Use GCC as the compiler instead of LLVM"
- In reply to: Dima Panov : "Re: git: 75ac7903573c - main - graphics/darktable: Use GCC as the compiler instead of LLVM"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 28 Jan 2023 14:51:01 UTC
Am 28.01.23 um 14:22 schrieb Dima Panov: > Moin-moin! > > > USES+= llvm:14,build > > with > > USES+= compiler:gcc-c++11-lib > USE_GCC=yes > > at same time? > Please choose only one set, compiler.mk have a higher priority and > conflicting with overriding CC > > BTW, USES=llvm also needs to set USE_CXXSTD='gnu++17', for example > Dima, thanks for looking again. I can't judge on the details because that's been Jean-Sébastien's doing, but I know that darktable uses two compilers: - one is for the C++ librawspeed and the C darktable code, and - the other compiler shall be LLVM to compile the OpenCL kernels. I don't think GCC could do the latter, and certainly darktable expects to use LLVM by way of its build tooling and configuration (cmake-based). Jean-Sébastien switched the C/C++ compiler from LLVM to GCC. If that raises conflicts, I wonder what those would be, and what to watch out for in the logs or at run-time, and that a "make reinstall" or "poudriere bulk -tC" would not catch. Both Jean-Sébastien and I, independently, have successful builds with both GCC and LLVM. I have not yet tested OpenCL at run-time though. So...? Cheers, Matthias