Building error of Zeal

[ivaquero]

I am a Mac M1 user, I got this error during building Zeal. I searched answer, it is raised by lack of Qt5WebEngine in qt@5 on Mac M1. Is there any workaround?

  "Qt5WebEngineWidgets" with any of the following names:

    Qt5WebEngineWidgetsConfig.cmake
    qt5webenginewidgets-config.cmake

  Add the installation prefix of "Qt5WebEngineWidgets" to CMAKE_PREFIX_PATH
  or set "Qt5WebEngineWidgets_DIR" to a directory containing one of the above
  files.  If "Qt5WebEngineWidgets" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  src/libs/browser/CMakeLists.txt:13 (find_package)


-- Configuring incomplete, errors occurred!
See also "/tmp/zeal-20211229-7242-cvbgtk/build/CMakeFiles/CMakeOutput.log".

[markwu]

Please change qt@5 to qt inside zeal.rb formula. I should be work.

[ivaquero]

I tried. However, I got this error.

  CMake did not find one.

  Could not find a package configuration file provided by "Qt5" with any of
  the following names:

    Qt5Config.cmake
    qt5-config.cmake

  Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
  to a directory containing one of the above files.  If "Qt5" provides a
  separate development package or SDK, be sure it has been installed.

-- Configuring incomplete, errors occurred!
See also "/tmp/zeal-20211230-72533-1u92ncl/build/CMakeFiles/CMakeOutput.log".

[markwu]

Do you uninstall qt@5?

[ivaquero]

Sure, I uninstalled. I found that the qt@5 does not have Arm support for WebEngineWidgets. And Zeal's cmake files require qt5.

I tried to find a workaround using Conda + Rosetta 2. However, the App was ''successfully built'', but when I clicked the buttons, it broke.

[markwu]

Sorry, then I have no idea.

I checked my qt dependency, it seems stay with qt@5 not qt. I think qt@5 is the right dependency. Maybe I messed up something in my local formula.

I removed everything related to qt, qt@5, zeal and rebuild it again with 'qt@5' , it just work.

But, my machine is intel-based macbook pro with macOS 11.6.2, maybe that's the reason.