-
Notifications
You must be signed in to change notification settings - Fork 78
Building Chromium packages #441
Comments
Are the Wayland development files installed? Have you managed to build Chromium without ozone-wayland for 32-bits before? |
Wayland development files are installed. No, I have never managed to build Chromium ozone-wayland for 32-bit before. |
Now I made gclient sync again, run ninja and have another error: |
Like I said in #439, this is not the best venue to discuss this kind of issue since it looks like you are having trouble building Chromium without oz-wl as well. Please try the chromium-packager and chromium-dev mailing lists instead. The error above is self-explanatory: you don't have freetype's 32-bit development headers. |
Thanks a lot. I just didn't find where I can find the chromium-packager or chromium-dev mailing list. |
Thank you very much! |
@vrotenberg have you checked the PKG_CONFIG_PATH? |
Yes. It's |
Have you followed all the steps here: Dependencies: |
I followed the instruction in this document: https://github.com/01org/ozone-wayland |
@vrotenberg Was there anything missing in our instructions resulting in this issue, if so can you update ReadME file, else lets close this one. |
I have this error after the patching. If I do git checkout master before running the patching everything is OK. But I need to run ./build/gyp_chromium after the patching and always get this error! |
While patching I have this message: |
Any suggestions? |
Hi!
I am trying to build Chromium for wayland for 32 bit machine. The GYP_DEFINES='component=static_library use_ash=1 use_aura=1 chromeos=0 use_ozone=1 use_xkbcommon=1 proprietary_codecs=1 ffmpeg_branding=Chrome target_arch=ia32 use_sysroot=0'
All patches applied successfully. While building (ninja -C out/Debug -j16 chrome) I have an error: "fatal error: 'wayland-client.h' file not found"
What did I wrong?
Thanks.
The text was updated successfully, but these errors were encountered: