Hacking the assistant.pro file to comment out relevant lines using
contains(QT_CONFIG, webkit), and adding:
defines += QT_NO_WEBKIT
then running the normal Qt configure and make seems to work well. otool
confirms that Assistant is not using webkit.
I'm still curious about the rationale for the -no-webkit configure option
only being for Windows though!
Tony
> Sent: Saturday, 20 April 2013 2:17 PM
>
> Hi Everybody,
>
> It seems this is not possible, -no-webkit is marked as Windows only in
the
> configure options docs, why is that? If Qt was smart enough to link to
the
> system webkit on Mac, it might make sense, but that doesn't happen.
>
> I would like to distribute my app via the Apple app store without
qtwebkit,
> and with qtassistant using QTextBrowser. This combination works well on
> Windows, yet QtAssistant will not build if -no-webkit is specified on the
> configure line on Mac. I have also tried running configure as normal,
then
> defining QT_NO_WEBKIT, and re-running the assistant makefile with -B. The
> assistant runs but still uses webkit. I can tell that since our help css
has first-
> child selectors in it, and they are working on Mac, but on Windows
> QTextBrowser ignores them.
>
> As a last resort, I could hack the supplied the assistant.pro to force it
to use
> QTextBrowser.
>
> I am using Qt 4.8.4, and gcc shows i686-apple-darwin11-llvm-gcc-4.2 on OSX
> 10.7.5.
>
> Thanks for any suggestions!
>
> Tony
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
