Kacvinsky, Tom wrote:
I still had problems finding stddef.h (included by cstddef), until I set the clang environment variable CPATH (which was set to the include paths generated by "gcc -v -xc++ /dev/null")That fixed the problem with cstddef, but now I have this problem: /home/BUILD64/bin/gcc-8.3.0-2/include/c++/8.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h> ^~~~~~~~~~ Not sure if this is a PySide2 problem or a LLVM (version 10, BTW) problem. I just find it out that the cstddef issue was fixed but not the cstdlib issue, as they have a similar chain of includes.
You said you have a custom build of llvm, yes? Did you configure the default set of include paths? The normal include paths would put the C++ includes first, followed by the C includes, and the use of "include_next" makes that mandatory. <cstdlib> is a C++ include, and "include_next" says "don't look everywhere for this file, instead start looking at the NEXT directory in the include list.
It is, frankly, an abomination, and if you can't figure out how to adjust the INLCUDE path, you should just change the "include_next" to "include". That should also solve the problem.
-- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ PySide mailing list PySide@qt-project.org https://lists.qt-project.org/listinfo/pyside
