Meson cannot find Cairo. #11713
-
Hello. While trying to build the Epiphany, I end receiving the following error message when calling "meson .." "Run-time dependency cairo found: NO (tried pkgconfig and cmake)" "../meson.build:80:0: ERROR: Dependency "cairo" not found, tried pkgconfig and cmake" I tried again, this time with: PKG_CONFIG_PATH=/media/34GB/Arquivos-de-Programas-Linux/Cairo-1.10.0/lib/pkgconfig/ meson .. To my surprise, it didn't work. The same error messages persisted. Then I gave a look at meson-log.txt. Three lines there that might be useful are: Determining dependency 'cairo' with pkg-config executable '/usr/bin/pkg-config' There is a thread on Unix stack exchange that tells to use: setenv PKG_CONFIG_PATH ${YOUR_PATH}/cairo/1.16.0/lib/pkgconfig However, setenv this not work here, so I am open to suggestions as to solve it. P.S:Also interest in know why: "PKG_CONFIG_PATH=/media/34GB/Arquivos-de-Programas-Linux/Cairo-1.10.0/lib/pkgconfig/ meson ." is not working, which seems absurd to me. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
Clearly it does work to set the env because that's exactly what the log file says has successfully happened. However it seems to me that you refer once to Cairo 1.16.0 and twice to Cairo 1.10.0, which version are you actually trying to use? What's the exact file path of the file "cairo.pc"? |
Beta Was this translation helpful? Give feedback.
-
Actually, there is not Cairo 1.16, this is from the internet thread suggesting to use setenv The file path to Cairo it is: /media/34GB/Arquivos-de-Programas-Linux/Cairo-1.10.0/lib/pkgconfig/ |
Beta Was this translation helpful? Give feedback.
-
Any ideas? |
Beta Was this translation helpful? Give feedback.
-
Ok, Meson 1.0.0 doesn't indicate the indirect dependencies. In my case there were a lot missing. It is absurd that it doesn't do so. Anyway, with 1.1.0 I was able to quickly pass all the missing dependencies, thanks for the help. |
Beta Was this translation helpful? Give feedback.
-
Anyways, yes, in general all meson can do is run pkg-config with the environment you give it. If you check the log file and set the same env manually then run the logged command, you should get the same results meson itself does. Meson 1.1.0 exposes error messages from pkg-config in the log file, thankfully, so this became a lot easier to debug. You can still do it with a bit of work in older versions too, though. |
Beta Was this translation helpful? Give feedback.
Can you try that with meson 1.1.0 instead of 1.0.0, it has better logging in the later version.