Thanks Israel,
I have done that for my application. The problem is that it also uses
Assistant, which on Mac requires webkit.
It's pretty silly - there doesn't seem to be a supported way of stopping
webkit from being in QT_CONFIG on Mac!
Regards,
Tony
Sent: Tuesday, 23 April 2013 1:56
Interesting. I went and actually looked at what was being built and QtWebKit is
being built in my configuration. And Assistant is actually using that library.
I guess since I start the build and go to sleep I never noticed if it was being
built or not. I don't link against it for my application
This is what I use on OS X 10.6.8 and 10.8 builds using the Qt 4.8.4
everywhere source package.
./configure -opensource -nomake demos -nomake examples -debug-and-release
-shared -fast -exceptions -stl -no-qt3support -no-webkit -no-phonon -largefile
-arch x86_64 -prefix
Thanks for the response Mike,
My configure used against expanded qt-everywhere-commercial-src-4.8.4.tar.gz
is:
./configure -arch x86 -no-qt3support -no-webkit -nomake examples -nomake
demos -sdk
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Develop
The only reliable way not to use webkit on both Mac and Windows, is to
erase the webkit* folders before configure.
Philippe
On Sat, 20 Apr 2013 16:00:47 +1000
Tony Rietwyk t...@rightsoft.com.au wrote:
Hacking the assistant.pro file to comment out relevant lines using
contains(QT_CONFIG,
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
